| 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: <m1prxhq0ni.fsf@ebiederm.dsl.xmission.com> Date: Fri, 07 Dec 2007 21:18:57 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Andrew Morton <akpm@...ux-foundation.org> Cc: Alexey Dobriyan <adobriyan@...il.com>, rjw@...k.pl, trond.myklebust@....uio.no, gnome42@...il.com, linux-kernel@...r.kernel.org, bfields@...ldses.org, den@...nvz.org Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression Andrew Morton <akpm@...ux-foundation.org> writes: > OK, perhaps a revert is the best thing to do here. I don't think anyone > will be expecting fully finalised and robust netns support in 2.6.24. I do think we expect /proc/net when the netns support is disabled to be as robust as it has been prior to 2.6.24, which is where we came in. The problem I tried to close one hole too many with my previous patch. The simplest thing to do and that will make things work for everyone in a tried and true fashion is not a complete revert but to simply remove d_revalidate (which is causing all of the trouble). We can figure out how to deal with the VFS mount handling not being friendly to network filesystems later. The implementation details of VFS mount handling do not lest us remove dcache entries for directories (even when they have been removed from the backing store) until we have removed all mounts from them and their children. Since I violated that rule. Kaboom! Eric -- 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