From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] dealing with proc_ns_follow_link() and "namespace" dentries
Date: Mon, 24 Nov 2014 10:55:36 +0000 [thread overview]
Message-ID: <20141124105536.GG7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20141101183037.GQ7996@ZenIV.linux.org.uk>
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?
next prev parent reply other threads:[~2014-11-24 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 6:29 [RFC] dealing with proc_ns_follow_link() and "namespace" dentries Al Viro
2014-10-13 22:42 ` Eric W. Biederman
2014-11-01 8:38 ` Al Viro
2014-11-01 15:06 ` Al Viro
2014-11-01 18:23 ` Eric W.Biederman
2014-11-01 18:38 ` Al Viro
2014-11-01 22:04 ` Al Viro
2014-11-01 18:30 ` Al Viro
2014-11-24 10:55 ` Al Viro [this message]
2014-10-14 0:41 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141124105536.GG7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).