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
| ||
|
Date: Tue, 7 May 2019 10:24:13 +0200 From: Ingo Molnar <mingo@...nel.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Waiman Long <longman9394@...il.com>, Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Will Deacon <will.deacon@....com>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [GIT PULL] locking changes for v5.2 * Linus Torvalds <torvalds@...ux-foundation.org> wrote: > On Mon, May 6, 2019 at 12:43 PM Ingo Molnar <mingo@...nel.org> wrote: > > > > Sure - how close is this to a straight: > > > > git revert 70800c3c0cc5 > > It's not really a revert. The code is different (and better) from the > straight revert, but perhaps equally importantly it also ends up with > a big comment about what's going on that made the original commit > wrong. > > So I'd suggest just taking the patch as-is, and not calling it a > revert. It may revert to the original _model_ of wakup list traversal, > but it does so differently enough that the patch itself is not a > revert. Ok, Waiman's patch is now the following commit in locking/urgent: a9e9bcb45b15: ("locking/rwsem: Prevent decrement of reader count before increment") it should get to you in a couple of days. Thanks, Ingo
Powered by blists - more mailing lists