Skip to contentSkip to conversation

x86/process: fix the misleading comment about PF_USER_WORKERs in copy_thread()

PATCH In review Oleg Nesterov 2 participants 3 messages Aug 20, 2025 – Aug 21, 2025 x86

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 x86/process: fix the misleading comment about PF_USER_WORKERs in copy_thread()

The comment says "doesn't return to ret_after_fork()" but in fact it should say "doesn't return from ret_from_fork()".

Plus the comment lacks some important details, and even "user space thread" doesn't look accurate, if nothing else this doesn't match the comment about PF_USER_WORKER in include/linux/sched.h.

---
 arch/x86/kernel/process.c | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)
arch/x86/kernel/process.c +9 -3
index e932e0e53972..cc4fe540d952 100644
@@ -237,14 +237,20 @@ int copy_thread(struct task_struct *p, const struct kernel_clone_args *args)
 
 	if (unlikely(args->fn)) {
 		/*
-		 * A user space thread, but it doesn't return to
-		 * ret_after_fork().
+		 * A non-PF_KTHREAD thread, but it doesn't return from
+		 * ret_from_fork().
+		 *
+		 * Either a PF_USER_WORKER kernel thread, in this case
+		 * arg->fn() must not return.
+		 * Or a user space task created by user_mode_thread(), in
+		 * this case arg->fn() can only return after a successful
+		 * kernel_execve().
 		 *
 		 * In order to indicate that to tools like gdb,
 		 * we reset the stack and instruction pointers.
 		 *
 		 * It does the same kernel frame setup to return to a kernel
-		 * function that a kernel thread does.
+		 * function that a PF_KTHREAD thread does.
 		 */
 		childregs->sp = 0;
 		childregs->ip = 0;
Signature · 1 line
2.25.1.362.g51ebf55
#1 lore raw
Quoted 10 lines · Oleg Nesterov
arch/x86/kernel/process.c +6 -2
 	if (unlikely(args->fn)) {
 		/*
-		 * A user space thread, but it doesn't return to
-		 * ret_after_fork().
+		 * A non-PF_KTHREAD thread, but it doesn't return from
+		 * ret_from_fork().
+		 *
+		 * Either a PF_USER_WORKER kernel thread, in this case
+		 * arg->fn() must not return.
+		 * Or a user space task created by user_mode_thread(), in

arch/x86/kernel/process.c int copy_thread(struct task_struct *p, const struct kernel_clone_args *args) · line 254

Quoted 10 lines
arch/x86/kernel/process.c +3 -1
+		 * this case arg->fn() can only return after a successful
+		 * kernel_execve().
 		 *
 		 * In order to indicate that to tools like gdb,
 		 * we reset the stack and instruction pointers.
 		 *
 		 * It does the same kernel frame setup to return to a kernel
-		 * function that a kernel thread does.
+		 * function that a PF_KTHREAD thread does.
 		 */

I'm not sure that comment clarifies things, especially the new paragraph. This does _not_ seem like the place to me to be explaining what the conventions are around arg->fn(). It would be better to put it near the definition or 'kernel_clone_args' or the place the function gets called, but not here.

#2 lore raw
Quoted 16 lines · Dave Hansen
Quoted 14 lines · Oleg Nesterov
arch/x86/kernel/process.c +8 -2
 	if (unlikely(args->fn)) {
 		/*
-		 * A user space thread, but it doesn't return to
-		 * ret_after_fork().
+		 * A non-PF_KTHREAD thread, but it doesn't return from
+		 * ret_from_fork().
+		 *
+		 * Either a PF_USER_WORKER kernel thread, in this case
+		 * arg->fn() must not return.
+		 * Or a user space task created by user_mode_thread(), in
+		 * this case arg->fn() can only return after a successful
+		 * kernel_execve().
 		 *
 		 * In order to indicate that to tools like gdb,
Quoted 8 lines

arch/x86/kernel/process.c int copy_thread(struct task_struct *p, const struct kernel_clone_args *args) · line 254

Quoted 6 lines
arch/x86/kernel/process.c +1 -1
 		 * we reset the stack and instruction pointers.
 		 *
 		 * It does the same kernel frame setup to return to a kernel
-		 * function that a kernel thread does.
+		 * function that a PF_KTHREAD thread does.
 		 */

I'm not sure that comment clarifies things,

OK, lets forger this patch then. But note that the 1st paragraph is obviously wrong.

Quoted 2 lines

especially the new
paragraph.

I was going to fix the typos in the 1st paragraph, then decided to add more details to clarify "doesn't return" and to "sync" this comment with the related comment in ret_from_fork().

And to make it clear that PF_USER_WORKER can never return to usermode, this connects to the recent discussion about PF_USER_WORKER && shstk.

Quoted 4 lines

This does _not_ seem like the place to me to be explaining what the conventions are around arg->fn(). It would be better to put it near the definition or 'kernel_clone_args' or the place the function gets called, but not here.

Not sure. To me this comment is more about kthread_frame_init() and ret_from_fork(). But I won't argue.

Oleg.