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: <m1d4v12056.fsf@ebiederm.dsl.xmission.com> Date: Fri, 26 Oct 2007 12:36:53 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Al Viro <viro@....linux.org.uk>, linux-kernel@...r.kernel.org, Pavel Emelyanov <xemul@...nvz.org>, Sukadev Bhattiprolu <sukadev@...ibm.com>, Linux Containers <containers@...ts.osdl.org> Subject: Re: [PATCH] proc: Fix proc_kill_inodes to kill dentries on all proc superblocks Linus Torvalds <torvalds@...ux-foundation.org> writes: > On Fri, 26 Oct 2007, Eric W. Biederman wrote: >> >> It appears we overlooked support for removing generic proc files >> when we added support for multiple proc super blocks. Handle >> that now. > > There seems to be more users of "proc_mnt" out there. proc_flush_task, > anyone? Yes. I've seen those and I do have some patches in my queue to address those. Technically none of those causes us to do the wrong thing in the presence of multiple proc superblocks, by the usage of proc_mnt. It still looks worth it to see if we can kill all of the users of proc_mnt. proc_flush_task is technically ok in it's usage of proc_mnt. It is just using it as what appears to be an unnecessary optimization. However the added complexity is currently hiding another bug. We call proc_flush_task_mnt with the wrong arguments. Further I haven't convinced myself the call to pid_ns_release_proc does not have some strange race in there, although there is nothing obviously wrong there. 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