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+55aFyx1+JCs7BuU1TvQ5LzUHaijWV3q-e65g=JCgBkXZFvYA@mail.gmail.com>
Date:	Sat, 12 Mar 2016 11:51:06 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ming Lei <tom.leiming@...il.com>
Cc:	Kent Overstreet <kent.overstreet@...il.com>,
	Ming Lin <mlin@...nel.org>, Jens Axboe <axboe@...nel.dk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: e827091cb1 "block: merge: get the 1st and last bvec via helpers" broken

On Sat, Mar 12, 2016 at 6:39 AM, Ming Lei <tom.leiming@...il.com> wrote:
>
> I am fine with either way, and I will prepare one patch and let Jens
> decide.

So guys, this needs to be done *now*.

And Jens - this is the last time I believe you when you say late
patches are required.

The buggy patch that introduced this problem was part of that very
late pull request that I already rejected once, and you then claimed
was absolutely required.

So the dicking around with the block layer stops *now*.

Seriously. I'm pissed off.

I don't want to see anything even half-way questionable during the
whole next release window. Not even during the merge window. You need
to do some serious quality control, and re-think the whole "large
changes" model.

            Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ