linux-kernel - Re: [PATCH v2] block: schedule queue restart after BLK_STS_ZONE

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]

Message-Id: <163528565626.259196.4840508461738349119.b4-ty@kernel.dk>
Date:   Tue, 26 Oct 2021 16:00:56 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Naohiro Aota <naohiro.aota@....com>
Cc:     linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        Christoph Hellwig <hch@....de>,
        Niklas Cassel <Niklas.Cassel@....com>
Subject: Re: [PATCH v2] block: schedule queue restart after BLK_STS_ZONE_RESOURCE

On Wed, 27 Oct 2021 01:51:27 +0900, Naohiro Aota wrote:
> When dispatching a zone append write request to a SCSI zoned block device,
> if the target zone of the request is already locked, the device driver will
> return BLK_STS_ZONE_RESOURCE and the request will be pushed back to the
> hctx dipatch queue. The queue will be marked as RESTART in
> dd_finish_request() and restarted in __blk_mq_free_request(). However, this
> restart applies to the hctx of the completed request. If the requeued
> request is on a different hctx, dispatch will no be retried until another
> request is submitted or the next periodic queue run triggers, leading to up
> to 30 seconds latency for the requeued request.
> 
> [...]

Applied, thanks!

[1/1] block: schedule queue restart after BLK_STS_ZONE_RESOURCE
      commit: 9586e67b911c95ba158fcc247b230e9c2d718623

Best regards,
-- 
Jens Axboe