linux-kernel - Re: [PATCH] block: Fix default IO priority if there is no IO context

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: <175399575406.610680.10505836643407350567.b4-ty@kernel.dk>
Date: Thu, 31 Jul 2025 15:02:34 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Bart Van Assche <bvanassche@....org>
Subject: Re: [PATCH] block: Fix default IO priority if there is no IO
 context


On Wed, 30 Jul 2025 21:49:53 -0700, Guenter Roeck wrote:
> Upstream commit 53889bcaf536 ("block: make __get_task_ioprio() easier to
> read") changes the IO priority returned to the caller if no IO context
> is defined for the task. Prior to this commit, the returned IO priority
> was determined by task_nice_ioclass() and task_nice_ioprio(). Now it is
> always IOPRIO_DEFAULT, which translates to IOPRIO_CLASS_NONE with priority
> 0. However, task_nice_ioclass() returns IOPRIO_CLASS_IDLE, IOPRIO_CLASS_RT,
> or IOPRIO_CLASS_BE depending on the task scheduling policy, and
> task_nice_ioprio() returns a value determined by task_nice(). This causes
> regressions in test code checking the IO priority and class of IO
> operations on tasks with no IO context.
> 
> [...]

Applied, thanks!

[1/1] block: Fix default IO priority if there is no IO context
      commit: e2ba58ccc9099514380c3300cbc0750b5055fc1c

Best regards,
-- 
Jens Axboe