| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5273F1ED.70408@redhat.com> Date: Fri, 01 Nov 2013 14:24:45 -0400 From: Prarit Bhargava <prarit@...hat.com> To: Mel Gorman <mgorman@...e.de> CC: Rik van Riel <riel@...hat.com>, Peter Zijlstra <peterz@...radead.org>, mingo@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH -v2 -tip] fix race between stop_two_cpus and stop_cpus On 11/01/2013 10:47 AM, Mel Gorman wrote: > On Fri, Nov 01, 2013 at 10:41:46AM -0400, Rik van Riel wrote: >> Subject: fix race between stop_two_cpus and stop_cpus >> >> There is a race between stop_two_cpus, and the global stop_cpus. >> >> It is possible for two CPUs to get their stopper functions queued >> "backwards" from one another, resulting in the stopper threads >> getting stuck, and the system hanging. This can happen because >> queuing up stoppers is not synchronized. >> >> This patch adds synchronization between stop_cpus (a rare operation), >> and stop_two_cpus. >> >> Signed-off-by: Rik van Riel <riel@...hat.com> >> --- >> v2: use lglock, as suggested by Peter & Mel, thanks to both of you >> for insisting on nicer code :) >> > > This is a tad more comprehensible :). Thanks! > > Acked-by: Mel Gorman <mgorman@...e.de> > This ran all morning without issues. Tested-by: Prarit Bhargava <prarit@...hat.com> P. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists