[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180717183450.GL2494@hirez.programming.kicks-ass.net>
Date: Tue, 17 Jul 2018 20:34:50 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Isaac J. Manjarres" <isaacm@...eaurora.org>
Cc: matt@...eblueprint.co.uk, mingo@...nel.org, tglx@...utronix.de,
bigeasy@...utronix.de, linux-kernel@...r.kernel.org,
psodagud@...eaurora.org, gregkh@...uxfoundation.org,
pkondeti@...eaurora.org, stable@...r.kernel.org
Subject: Re: [PATCH v4] stop_machine: Disable preemption after queueing
stopper threads
On Tue, Jul 17, 2018 at 09:30:17AM -0700, Isaac J. Manjarres wrote:
> After cpu_stop_queue_two_works() queues the cpu_stop works
> for the stopper threads, it releases the locks held for
> both threads, which enables preemption, which allows the
> following race condition to occur:
Does not apply because an earlier version is already applied.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/kernel/stop_machine.c?id=9fb8d5dc4b649dd190e1af4ead670753e71bf907
if there still is a problem, please send a new patch that describes the
remaining problem.
Powered by blists - more mailing lists