[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250926152154.MYtjJh-Q@linutronix.de>
Date: Fri, 26 Sep 2025 17:21:54 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Edward Adam Davis <eadavis@...com>, kees@...nel.org,
akpm@...ux-foundation.org, 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 2025-09-26 17:11:12 [+0200], Vlastimil Babka wrote:
> 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
A pull request has been sent to Linus earlier today.
Sebastian
Powered by blists - more mailing lists