From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git pile 2
Date: Tue, 16 Dec 2014 13:33:30 +0000 [thread overview]
Message-ID: <20141216133330.GB22149@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20141215235124.GX22149@ZenIV.linux.org.uk>
On Mon, Dec 15, 2014 at 11:51:25PM +0000, Al Viro wrote:
> Next pile (and there'll be one or two more). The large piece in this one is
> getting rid of /proc/*/ns/* weirdness; among other things, it allows to
> (finally) make nameidata completely opaque outside of fs/namei.c, making for
> easier further cleanups in there.
>
> I have _not_ included removal of unshare_fs_struct() into that pile; I think
> it'll turn out to be OK, but it's clearly the next cycle fodder.
... but I have included the "obviously safe" patch separating PID 1
->fs. Without letting it sit in -next long enough. And it turns out
to be not safe at all - it might be salvagable, but not in this form.
Mea maxima culpa - I should've known better than that. Self-LART applied;
please, drop this pull request, I'll send a saner one (for stuff that *did*
sit in -next long enough) in a bit.
Again, my apologies ;-/
next prev parent reply other threads:[~2014-12-16 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:51 [git pull] vfs.git pile 2 Al Viro
2014-12-16 13:33 ` Al Viro [this message]
2014-12-16 18:06 ` Al Viro
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 12:38 [git pull] vfs.git, " Al Viro
2016-12-16 22:12 [git pull] vfs.git " Al Viro
2016-12-18 2:49 ` Linus Torvalds
2016-12-18 3:26 ` Al Viro
2016-12-18 3:34 ` Linus Torvalds
2016-12-18 4:06 ` Al Viro
2016-12-18 23:40 ` Darrick J. Wong
2013-05-04 20:23 Al Viro
2012-10-12 1:19 [git pull] vfs.git, " 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=20141216133330.GB22149@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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