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, 18 May 2010 16:02:11 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Greg KH <greg@...ah.com>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: build failure after merge of the driver-core tree On Tue, May 18, 2010 at 03:35:10AM -0700, Eric W. Biederman wrote: > Thanks. > > I will cook up a proper incremental patch after I get some sleep. Stephen > it appears those two lines you have commented out are actually unnecessary. > > We have > deactivate_super > kill_sb aka sysfs_kill_sb > kill_anon_super > generic_shutdown_super > sb_lock > list_del(sb->s_instances) > sb_unlock > kfree(info) > > Nothing generic stomps on s_fs_info. > > Which means that if I find a superblock on sb->s_instances sb->s_fs_info > still points to a valid sysfs_super_info. Except that sb_lock is going away next cycle. There are very few users left outside of fs/super.c and I'd much prefer it to become static. -- 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