tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS head: 8723dc57de6371f9cc8764e15d4cc9e57ae592ee commit: 0b7ab5fb231754def820e514cc7607bbad377928 [1755/1755] futex: Prevent exit livelock config: x86_64-buildonly-randconfig-2002-20250811 (https://download.01.org/0day-ci/archive/20250815/202508151048.nycUlzlC-lkp@i...) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250815/202508151048.nycUlzlC-lkp@i...) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202508151048.nycUlzlC-lkp@intel.com/ All warnings (new ones prefixed by >>):

...

kernel/futex.c:1209: warning: Function parameter or member 'ret' not described in 'wait_for_owner_exiting'

vim +1209 kernel/futex.c 1201 1202 /** 1203 * wait_for_owner_exiting - Block until the owner has exited 1204 * @exiting: Pointer to the exiting task 1205 * 1206 * Caller must hold a refcount on @exiting. 1207 */ 1208 static void wait_for_owner_exiting(int ret, struct task_struct *exiting)

1209 { 1210 if (ret != -EBUSY) { 1211 WARN_ON_ONCE(exiting); 1212 return; 1213 } 1214 1215 if (WARN_ON_ONCE(ret == -EBUSY && !exiting)) 1216 return; 1217 1218 mutex_lock(&exiting->futex_exit_mutex); 1219 /* 1220 * No point in doing state checking here. If the waiter got here 1221 * while the task was in exec()->exec_futex_release() then it can 1222 * have any FUTEX_STATE_* value when the waiter has acquired the 1223 * mutex. OK, if running, EXITING or DEAD if it reached exit() 1224 * already. Highly unlikely and not a problem. Just one more round 1225 * through the futex maze. 1226 */ 1227 mutex_unlock(&exiting->futex_exit_mutex); 1228 1229 put_task_struct(exiting); 1230 } 1231

-- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki