| 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, 4 Apr 2007 08:57:38 -0400 (EDT) From: "John Anthony Kazos Jr." <jakj@...-k-j.com> To: linux-ext4@...r.kernel.org Subject: (un)lock_kernel() ? Why does ext4_fill_super release the BKL on entry and take it on both normal and abnormal exit? As far as I can see, ext4_fill_super is called by get_sb_bdev, which calls the ->get_sb method without the BKL, and ext4_get_sb calls get_sb_bdev without the BKL. And the ext2 code does not touch the BKL in ext2_fill_super. Is the VFS code going to be changed somewhere in the future and it's being anticipated, or is this a bug? - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists