linux-kernel - Re: [RFC] dealing with proc_ns_follow

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 24 Nov 2014 10:55:36 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] dealing with proc_ns_follow_link() and "namespace" dentries

On Sat, Nov 01, 2014 at 06:30:37PM +0000, Al Viro wrote:
> On Sat, Nov 01, 2014 at 03:06:20PM +0000, Al Viro wrote:
> > On Sat, Nov 01, 2014 at 08:38:04AM +0000, Al Viro wrote:
> > > OK, interim branch (_completely_ untested, and there's quite a bit of
> > > work remaining) is in vfs.git#nsfs.
> > 
> > ... except that what got pushed was completely buggered - the last changes
> > not committed *and* include/linux/ns_common.h not git-add'ed at the very
> > beginning.  Oh, well - it wasn't hard to reconstruct its history...
> > 
> > Anyway, that much got fixed and pushed; sorry about the noise - shouldn't
> > have posted before grabbing some sleep...
> 
> And now it even seems to work.  Poking in /proc/*/ns/*, mount --bind of those
> suckers to regular files, unshare and nsenter (both by PID and by file,
> including the ones we'd bound somewhere).  Eric, could you hit it with
> whatever testsuite you are using and see if it survives?
> 
> It's vfs.git#nsfs (head should be at 2e64120), branched at -rc2.  The meat
> of that sucker is in the next-to-last commit; the rest is preparation and
> a minor cleanup.

ping?
--
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/