| 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, 26 Oct 2010 17:24:34 -0400 From: "J. Bruce Fields" <bfields@...ldses.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Arnd Bergmann <arnd@...db.de>, Bryan Schumaker <bjschuma@...app.com>, linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: nfsd changes for 2.6.37 On Tue, Oct 26, 2010 at 02:02:05PM -0700, Linus Torvalds wrote: > On Tue, Oct 26, 2010 at 1:55 PM, Arnd Bergmann <arnd@...db.de> wrote: > > > > Finally, we can build fs/locks.c, nfs and nfsd with CONFIG_BKL > > disabled. > > > > *not tested* > > Ok, please make this so, so that we finally can effectively get rid of > the BKL in this release (I don't really care about the random old > drivers that may be "depends on BKL"). > > But that obviously requires at least some minimal testing by somebody > who is using NFS heavily, including locking. I assume that the > connectathon tests include file locking? And I presume that the nfs > developers run those at least semi-regularly and could do at least > that kind of minimal testing? I did a couple connectathon runs just now with no obvious ill effects except for some sleep-within-spinlock warnings in the lease code. Yeah, connecthon does include lock tests, though they're just basic correctness tests. --b. -- 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