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: Wed, 30 Apr 2014 16:04:58 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Al Viro <viro@...iv.linux.org.uk> Cc: Miklos Szeredi <miklos@...redi.hu>, Dave Chinner <david@...morbit.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org> Subject: Re: dcache shrink list corruption? On Wed, Apr 30, 2014 at 3:12 PM, Al Viro <viro@...iv.linux.org.uk> wrote: > > I've just pushed the whole thing to vfs.git#for-linus; > review and testing would be very welcome. I have no half-way relevant test-case for this, so I'm hoping people who have good VFS stress-tests (preferably under memory pressure so that we get that whole shrinking path) will test. But it looks fine. That said, I do hate that RCU read-lock around the final spin-unlock. Let me go talk to the paravirt people. Maybe they don't need this, and I don't know exactly *how* they use that lock pointer after the unlock in the "kick waiters" part. Maybe it's all good. Linus -- 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