From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [revert] commit e9496ff46a20a8592fdc7bdaaf41b45eb808d310 needs to be reverted
Date: Thu, 17 Dec 2009 20:37:26 +0000 [thread overview]
Message-ID: <20091217203726.GE18217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20091217202613.GD18217@ZenIV.linux.org.uk>
On Thu, Dec 17, 2009 at 08:26:13PM +0000, Al Viro wrote:
> On Thu, Dec 17, 2009 at 01:49:34PM -0500, Eric Paris wrote:
> > I pulled from Linus Dec16 and didn't have problems. This is a pull from
> > Dec17, plus some of my own patches which I'd be surprised to learn were
> > related. I have an NFS mount in my fstab, I assume this is that being
> > mounted on boot. I'll start a bisect if needed, but maybe someone will
> > know what they broke instantly....
>
> Gyah... Please, revert e9496ff46a20a8592fdc7bdaaf41b45eb808d310;
> it's dependent on a lot of other stuff not currently in mainline
> and badly broken with current fs/namespace.c. Sorry, badly out-of-order
> cherry-pick from old queue.
PS: there's a large pending series reworking the refcounting and lifetime
rules for vfsmounts that will, among other things, allow to rip a subtree
away _without_ dissolving connections in it, to be garbage-collected
when all active references are gone. It's considerably saner wrt "is
the subtree busy" logics, but it's nowhere near being ready for merge
at the moment; this changeset is one of the things becoming possible
with that sucker, but it certainly shouldn't have been picked during this
cycle. My apologies...
prev parent reply other threads:[~2009-12-17 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 18:49 NULL pointer dereference in commit_tree() from Linus' Dec17 tree Eric Paris
2009-12-17 20:23 ` Eric Paris
2009-12-17 20:26 ` [revert] commit e9496ff46a20a8592fdc7bdaaf41b45eb808d310 needs to be reverted Al Viro
2009-12-17 20:37 ` Al Viro [this message]
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=20091217203726.GE18217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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