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: Mon, 21 Jun 2010 16:38:13 +0200 From: Oleg Nesterov <oleg@...hat.com> To: Andrew Morton <akpm@...ux-foundation.org>, Pavel Emelyanov <xemul@...nvz.org>, Linux Containers <containers@...ts.osdl.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] procfs: Do not release pid_ns->proc_mnt too early On 06/21, Louis Rilling wrote: > > On 18/06/10 19:55 +0200, Oleg Nesterov wrote: > > > Yes, this should be fixed, I already realized this. work->func(ns) is > > called when ns is already fixed. > > > > Otherwise, nobody should use ns->proc_mount when ns is already dead/freed. > > I meant the opposite. proc_mnt can be kept mounted somewhere, I think, no. If it is kept mounted vfsmount should be different. > and accesses to it > will likely try to access (freed) pid_ns from it. Not sure, there must be no tasks (and pids) in this ns. By anyway I agree. This needs more thinking and we should do something with sb->s_fs_info. But given that nobody (including me) seem to like this approach - let's forget this patch. Thanks, Oleg. -- 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