linux-kernel - Re: [GIT PULL] block/IO bits for 2.6.35-rc1

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]

Date:	Sun, 06 Jun 2010 13:23:06 +0200
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	philipp.reisner@...bit.com
Subject: Re: [GIT PULL] block/IO bits for 2.6.35-rc1

On 2010-06-05 00:37, Linus Torvalds wrote:
> 
> 
> On Fri, 4 Jun 2010, Jens Axboe wrote:
>>
>> - A drbd update.
> 
> Can we agree to just stop this? 
> 
> During the merge window, please. The drbd fiasco has been going on too 
> long for me to believe in the whole "a few more fixes" thing.
> 
> If it's a security issue, or a major oops, take it. But don't send me 
> "updates" or stuff "just to make it work", since it never has before.
> 
> It's not a regression that drbd is in bad shape. So don't try to make it 
> out to be one. And if it's not a regression or a major oops/security 
> issue, it goes into the NEXT MERGE WINDOW.
> 
> Yes, I'm annoyed. Somebody needs to call out the drbd crud. I really don't 
> want _any_ more drbd crap after the merge window. If I see any more, I'll 
> stop pulling. Comprende?

Understood, I should have been a bit more strict on accepting
late drbd chages.

-- 
Jens Axboe

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