From: "Eric W.Biederman" <ebiederm@xmission.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
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: Sat, 01 Nov 2014 11:23:34 -0700 [thread overview]
Message-ID: <cfb295aa-0e4b-4185-875f-3745d2c5c01a@email.android.com> (raw)
In-Reply-To: <20141101150620.GP7996@ZenIV.linux.org.uk>
On November 1, 2014 8:06:20 AM PDT, Al Viro <viro@ZenIV.linux.org.uk> 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...
No worries. I am effectively without internet access right from now until about the 3rd week in November as I move so I really can't look anyway.
>From your description I am concerned about using the letter combination nsfs. I once used nsfd, and that was so close to nfsd that Linus got confused, and hilarity ensued. nsfs isn't quite as bad but the abbreviation still seems close enough to nfs that confusion could result.
Eric
next prev parent reply other threads:[~2014-11-01 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 6:29 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 [this message]
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
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=cfb295aa-0e4b-4185-875f-3745d2c5c01a@email.android.com \
--to=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome