linux-kernel - Re: [GIT PULL] Smaller btrfs pull

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFz-aSbmLoZv=CGY1bXpQ1zE935-FjTLMZF5=5hteyf9kg@mail.gmail.com>
Date:	Sat, 16 Aug 2014 09:11:41 -0600
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Mason <clm@...com>
Cc:	linux-btrfs <linux-btrfs@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Smaller btrfs pull

On Fri, Aug 15, 2014 at 11:26 AM, Chris Mason <clm@...com> wrote:
>
> I've been running xfstests with these against your current git
> overnight, but I'm queueing up longer tests as well.  I understand
> you may want to wait until rc2, but either way I'll get a sane queue
> into my linux-next branch for the rest of the rcs.

You completely mis-understand.

If something isn't appropriate for the merge window, then it sure as
HELL isn't appropriate for later rc's either.

So I'm not going to pull some "stragglers" later and just pull some
initial stuff now. That's not how this works.

The changes for the merge window should have been ready *before* the
merge window even opened. That has always been the rule. We don't do
random development and re-organization during the merge window, and we
certainly do not do it *later*.

I'm going to pull this reduced set, but that in no way means that I
will then pull later sets after the merge window.  The stuff after the
merge window should be pure fixes, and I'm in fact going to be
stricter with btrfs than usual, because I think this was such a
disaster. Oopses, regressions, data corruption, security fixes, and
things like that *only*. No cleanups, no random crap, nothing that
doesn't count as critical.

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