linux-kernel - Re: [revert] commit e9496ff46a20a8592fdc7bdaaf41b45eb808d310 needs to be reverted

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]

Message-ID: <20091217203726.GE18217@ZenIV.linux.org.uk>
Date:	Thu, 17 Dec 2009 20:37:26 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: [revert] commit e9496ff46a20a8592fdc7bdaaf41b45eb808d310 needs
	to be reverted

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...
--
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/