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

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

Message-ID: <a65ca1ef-1c9a-4d40-8e11-d9dc2cc75e1e@gmail.com>
Date: Sat, 18 May 2024 08:52:54 +0800
From: Wu Bo <wubo.oduw@...il.com>
To: Bart Van Assche <bvanassche@....org>, 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
Subject: Re: [PATCH stable] block/mq-deadline: fix different priority request
 on the same zone

On 2024/5/18 01:53, Bart Van Assche wrote:
> 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.
Hi Bart,

Yes, I noticed that 'zone write plugging' has been merged to latest
branch. But it seems hard to backport to old version which mq-deadline
priority feature has been merged. So is it possible to apply this fix to
old versions?

Thanks,
Wu Bo
>
> Thanks,
>
> Bart.