linux-kernel - Re: [PATCH V8 0/3] blk-mq: refactor code of issue request directly

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 5 Dec 2018 11:01:52 +0800
From:   "jianchao.wang" <jianchao.w.wang@...cle.com>
To:     Jens Axboe <axboe@...nel.dk>
Cc:     ming.lei@...hat.com, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V8 0/3] blk-mq: refactor code of issue request directly



On 12/5/18 10:58 AM, Jens Axboe wrote:
> On 11/14/18 8:12 PM, Jianchao Wang wrote:
>> Hi Jens
>>
>> Please consider this patchset for 4.21.
>> It refactors the code of issue request directly to unify the interface
>> and make the code clearer and more readable.
>>
>> The 1st patch refactors the code of issue request directly to unify the
>> helper interface which could handle all the cases.
>>
>> The 2nd patch make blk_mq_sched_insert_requests issue requests directly
>> with 'bypass' false, then it needn't to handle the non-issued requests
>> any more.
>>
>> The 3rd patch replace and kill the blk_mq_request_issue_directly.
> 
> I'd love to get this queued up, the direct dispatch path is a mess and
> it's even now been known to cause corruptions... I'm going to queue
> up the direct dispatch fix shortly, and apply it to for-4.21/block
> as well. Any chance you can respin this on top after that?
> 

OK, I will do now.

Thanks
Jianchao