| 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: <4AF9DD24.8060501@lougher.demon.co.uk> Date: Tue, 10 Nov 2009 21:37:40 +0000 From: Phillip Lougher <phillip@...gher.demon.co.uk> To: Phillip Lougher <phillip@...gher.demon.co.uk> CC: Andrew Morton <akpm@...ux-foundation.org>, jblunck@...e.de, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, matthew@....cx, viro@...iv.linux.org.uk Subject: Re: BKL: Remove BKL from Squashfs Phillip Lougher wrote: > This patch was prompted by Jan Blunck's "Push down BKL to the > filesystems" patch > series, where he firstly pushes the BKL down to individual filesystems > (even if they don't need it) , and then successively removes them > (on a one patch per filesystem basis) in later patches. > > The patch should be reviewed in the context that it is intended for Jan's > BKL removal patch series. > Jan and/or Matthew, Can you please ACK this patch, and say whether you're going to add it to your BKL patch series? (I'm happy for it to go through there, rather than my Squashfs tree). After reviewing your patches, it seems to me that the BKL isn't needed in Squashfs. You removed it from 23 filesystems because it's not protecting any shared state, on that basis it isn't needed needed in Squashfs either. Thanks Phillip -- 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