linux-kernel - Re: [PATCH stable] block/mq-deadline: fix different priority request on the same 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] [thread-next>] [day] [month] [year] [list]

Date: Fri, 17 May 2024 10:53:35 -0700
From: Bart Van Assche <bvanassche@....org>
To: Wu Bo <bo.wu@...o.com>
Cc: axboe@...nel.dk, dlemoal@...nel.org, linux-block@...r.kernel.org,
 linux-kernel@...r.kernel.org, stable@...r.kernel.org, wubo.oduw@...il.com
Subject: Re: [PATCH stable] block/mq-deadline: fix different priority request
 on the same zone

On 5/16/24 18:44, Wu Bo wrote:
> So I figured this solution to fix this priority issue on zoned device. It sure
> raises the overhead but can do fix it.

Something I should have realized earlier is that this patch is not
necessary with the latest upstream kernel (v6.10-rc1). Damien's zoned
write plugging patch series has been merged. Hence, I/O schedulers,
including the mq-deadline I/O schedulers, will only see a single
zoned write at a time per zone. So it is no longer possible that
zoned writes are reordered by the I/O scheduler because of their I/O
priorities.

Thanks,

Bart.