From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,Kartikey406@gmail.com,brauner@kernel.org,oleg@redhat.com,akpm@linux-foundation.org
Subject: [folded-merged] kernel-fork-validate-exit_signal-in-kernel_clone-fix.patch removed from -mm tree
Date: Fri, 03 Apr 2026 10:59:41 -0700 [thread overview]
Message-ID: <20260403175942.43ABFC4CEF7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kernel-fork-validate-exit_signal-in-kernel_clone-fix
has been removed from the -mm tree. Its filename was
kernel-fork-validate-exit_signal-in-kernel_clone-fix.patch
This patch was dropped because it was folded into kernel-fork-validate-exit_signal-in-kernel_clone.patch
------------------------------------------------------
From: Oleg Nesterov <oleg@redhat.com>
Subject: kernel-fork-validate-exit_signal-in-kernel_clone-fix
Date: Thu, 19 Mar 2026 18:16:49 +0100
the comment above kernel_clone() should be updated
Link: https://lkml.kernel.org/r/abwvgU17W8wuW2-J@redhat.com
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/fork.c | 2 --
1 file changed, 2 deletions(-)
--- a/kernel/fork.c~kernel-fork-validate-exit_signal-in-kernel_clone-fix
+++ a/kernel/fork.c
@@ -2611,8 +2611,6 @@ struct task_struct *create_io_thread(int
*
* 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)
{
_
Patches currently in -mm which might be from oleg@redhat.com are
kernel-fork-validate-exit_signal-in-kernel_clone.patch
reply other threads:[~2026-04-03 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260403175942.43ABFC4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=Kartikey406@gmail.com \
--cc=brauner@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@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