linux-kernel - Re: [GIT PULL] block/io bits for 2.6.35-rc

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: <AANLkTilnMnUhOFecDdqDJrkGki-6HeDMH4sVGp0lN66g@mail.gmail.com>
Date:	Thu, 10 Jun 2010 10:03:55 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Christoph Hellwig <hch@....de>
Cc:	Jens Axboe <jaxboe@...ionio.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] block/io bits for 2.6.35-rc

On Thu, Jun 10, 2010 at 9:40 AM, Christoph Hellwig <hch@....de> wrote:
>
> Maybe give it a bit more beating in linux-next and send it off to Linus
> once he's back from his vacation?

Yes, I'd probably be happier with that. As long as it's "just" a
performance regression (and clearly not one that actually affects most
people all that noticeably), I'd much rather not have to worry about
any potential new issues being introduced right now.

So I'm more looking for "let's fix catastrophic events" for -rc3.
After I get back, I'm way more open to "let's fix any real bugs",
because then I can at least react to any fallout.

(I'm planning on trying to roughly keep up on email etc - I'm today
doing all my email using gmail to test how well that works as an
alternative to my usual "inside two firewalls" behavior. But I'm
seriously trying to avoid even having a laptop with me, because if I
have something where I can do kernel development and git pulls, I know
I'm not going to be just on vacation).

                    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/