From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,oleg@redhat.com,kees@kernel.org,david@redhat.com,eadavis@qq.com,akpm@linux-foundation.org
Subject: [alternative-merged] copy_process-fixed-jump-logic-error.patch removed from -mm tree
Date: Fri, 26 Sep 2025 12:55:46 -0700 [thread overview]
Message-ID: <20250926195547.1B4BEC113CF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: copy_process(): fix jump logic error
has been removed from the -mm tree. Its filename was
copy_process-fixed-jump-logic-error.patch
This patch was dropped because an alternative patch was or shall be merged
------------------------------------------------------
From: Edward Adam Davis <eadavis@qq.com>
Subject: copy_process(): fix jump logic error
Date: Wed, 24 Sep 2025 20:06:21 +0800
After futex_hash_allocate_default() fails, the logic should jump to
bad_fork_cancel_cgroup, not bad_fork_core_free.
Jumping to bad_fork_core_free would cause a siglock imbalance.
Link: https://lkml.kernel.org/r/tencent_5E4F978D9525A58D97925ADDBADDB2193107@qq.com
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Kees Cook <kees@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/fork.c~copy_process-fixed-jump-logic-error
+++ a/kernel/fork.c
@@ -2293,7 +2293,7 @@ __latent_entropy struct task_struct *cop
if (need_futex_hash_allocate_default(clone_flags)) {
retval = futex_hash_allocate_default();
if (retval)
- goto bad_fork_core_free;
+ goto bad_fork_cancel_cgroup;
/*
* If we fail beyond this point we don't free the allocated
* futex hash map. We assume that another thread will be created
_
Patches currently in -mm which might be from eadavis@qq.com are
reply other threads:[~2025-09-26 19:55 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=20250926195547.1B4BEC113CF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=eadavis@qq.com \
--cc=kees@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 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.