From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Minu Jin <s9430939@naver.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, akpm@linux-foundation.org,
david@kernel.org, kees@kernel.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, Liam.Howlett@oracle.com, vbabka@suse.cz,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] fork: clarify copy_mm() comment for kernel thread
Date: Tue, 27 Jan 2026 09:25:26 +0000 [thread overview]
Message-ID: <d8d4dc93-78ab-47e5-8daf-36fd9468ed97@lucifer.local> (raw)
In-Reply-To: <20260127055321.2400480-1-s9430939@naver.com>
On Tue, Jan 27, 2026 at 02:53:21PM +0900, Minu Jin wrote:
> The existing comment is misleading:
>
> 1. "steal a active VM" suggests this code performs the active_mm
> borrowing, but the actual borrowing happens in context_switch()
> where 'next->active_mm = prev->active_mm' is assigned.
> This code simply returns 0 to skip mm copying for kernel threads.
Yeah but the comment as it stands implies that you are doing that elsewhere
so I don't think this is a problem.
Referring to a specific other function in a comment unnecessarily makes
bitrot easier.
>
> 2. "active VM" is outdated terminology, the kernel uses "active_mm".
Well VM refers to the virtual address space so it's perfectly fine
terminology.
>
> Update the comment to accurately describe what this code does.
I hate to say it but this sort of enumerated list is very AI-like so if you
are sending a patch that is AI-generated please do indicate that this is so
(and put e.g. Co-Developed-by: <whatever>) if so.
>
> Signed-off-by: Minu Jin <s9430939@naver.com>
Thanks for the patch but I honestly don't think this is all that
misleading. This original comment is from 2005 and I don't think anybody's
been all that confused by it in the meantime.
So I don't think we should take this.
Cheers, Lorenzo
> ---
> kernel/fork.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index b1f3915d5f8e..4bfd606004db 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1566,9 +1566,10 @@ static int copy_mm(u64 clone_flags, struct task_struct *tsk)
> tsk->active_mm = NULL;
>
> /*
> - * Are we cloning a kernel thread?
> + * Kernel threads have no 'mm' of their own as they borrow the
> + * 'active_mm' from the previous process at context_switch().
> *
> - * We need to steal a active VM for that..
> + * Return 0 directly to skip the copy_mm process.
> */
> oldmm = current->mm;
> if (!oldmm)
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-01-27 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 5:53 Minu Jin
2026-01-27 9:25 ` Lorenzo Stoakes [this message]
2026-01-27 9:40 ` Minu Jin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8d4dc93-78ab-47e5-8daf-36fd9468ed97@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=s9430939@naver.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox