sched/rseq: Fix concurrency ID handling of usermodehelper kthreads
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Mon, 2 Jan 2023 15:12:16 +0000 (10:12 -0500)
committerBorislav Petkov (AMD) <bp@alien8.de>
Mon, 2 Jan 2023 15:34:12 +0000 (16:34 +0100)
commitbbd0b031509b880b4e9a880bb27ca2a30ad081ab
tree3c16b06a9c0bc653348674cbc9dd5b743897f660
parentc89970202a1153b2fc230e89f90c180bd5bcbcef
sched/rseq: Fix concurrency ID handling of usermodehelper kthreads

sched_mm_cid_after_execve() does not expect NULL t->mm, but it may happen
if a usermodehelper kthread fails when attempting to execute a binary.

sched_mm_cid_fork() can be issued from a usermodehelper kthread, which
has t->flags PF_KTHREAD set.

Fixes: af7f588d8f73 ("sched: Introduce per-memory-map concurrency ID")
Reported-by: kernel test robot <yujie.liu@intel.com>
Reported-by: Borislav Petkov <bp@alien8.de>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/oe-lkp/202212301353.5c959d72-yujie.liu@intel.com
kernel/sched/core.c