linux-kernel - Re: two more fixes for block/for-linus

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: <54202CF9.7050303@kernel.dk>
Date:	Mon, 22 Sep 2014 08:06:49 -0600
From:	Jens Axboe <axboe@...nel.dk>
To:	Christoph Hellwig <hch@....de>
CC:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: two more fixes for block/for-linus

On 2014-09-22 07:59, Christoph Hellwig wrote:
> Fix two regressions with the timer/blk_mq_start_request changes found
> when using scsi-mq on an ATA device.
>
> Note that given how late we are in the cycle I wonder if we really should
> push the changes in block/for-linus to Linus in this cycle.  The race
> part of the timer fixes is extremly narrow, and the reserved request
> part of it requires an out of tree driver update to trigger it, so it
> doesn't sound super criticial.

I was planning on pushing it out today, I've run a lot of testing on it 
internally last week. Ho hum, let me think about it...

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