From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, vschneid@redhat.com,
vincent.guittot@linaro.org, vbabka@kernel.org, surenb@google.com,
rppt@kernel.org, rostedt@goodmis.org, peterz@infradead.org,
mingo@redhat.com, mhocko@suse.com, mgorman@suse.de,
ljs@kernel.org, Liam.Howlett@oracle.com, kees@kernel.org,
Kartikey406@gmail.com, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, david@kernel.org, bsegall@google.com,
brauner@kernel.org
Subject: [PATCH -mm] kernel-fork-validate-exit_signal-in-kernel_clone-fix
Date: Thu, 19 Mar 2026 18:16:49 +0100 [thread overview]
Message-ID: <abwvgU17W8wuW2-J@redhat.com> (raw)
In-Reply-To: <20260316154206.C5CA4C19421@smtp.kernel.org>
Andrew, can you fold this trivial fixup into
kernel-fork-validate-exit_signal-in-kernel_clone.patch
? the comment above kernel_clone() shoule be updated.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
kernel/fork.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index 646ae6f2ed93..a12febb8822c 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -2614,8 +2614,6 @@ struct task_struct *create_io_thread(int (*fn)(void *), void *arg, int node)
*
* It copies the process, and if successful kick-starts
* it and waits for it to finish using the VM if required.
- *
- * args->exit_signal is expected to be checked for sanity by the caller.
*/
pid_t kernel_clone(struct kernel_clone_args *args)
{
--
2.52.0
prev parent reply other threads:[~2026-03-19 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 15:42 + kernel-fork-validate-exit_signal-in-kernel_clone.patch added to mm-nonmm-unstable branch Andrew Morton
2026-03-19 17:16 ` Oleg Nesterov [this message]
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=abwvgU17W8wuW2-J@redhat.com \
--to=oleg@redhat.com \
--cc=Kartikey406@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=ljs@kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.