[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6777d66-a55d-46ef-b972-951eb48337b7@suse.cz>
Date: Fri, 26 Sep 2025 17:11:12 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Edward Adam Davis <eadavis@...com>, kees@...nel.org,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, akpm@...ux-foundation.org
Cc: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com, rostedt@...dmis.org,
bsegall@...gle.com, mgorman@...e.de, vschneid@...hat.com, david@...hat.com,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, rppt@...nel.org,
surenb@...gle.com, mhocko@...e.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH Next] copy_process(): Fixed jump logic error
On 9/24/25 14:06, Edward Adam Davis wrote:
> 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.
>
> Signed-off-by: Edward Adam Davis <eadavis@...com>
Sebastian already fixed this and it's in tip: locking/urgent
https://lore.kernel.org/all/20250918130945.-7SIRk8Z@linutronix.de/
> ---
> kernel/fork.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index e9a7fb5c3e49..a0b8eeeb1d27 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -2349,7 +2349,7 @@ __latent_entropy struct task_struct *copy_process(
> 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
Powered by blists - more mailing lists