linux-kernel - [PATCH v2 0/2] new struct io_work and use it in f2fs fsverity work

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-next>] [day] [month] [year] [list]

Message-ID: <20240701075138.1144575-1-yi.sun@unisoc.com>
Date: Mon, 1 Jul 2024 15:51:36 +0800
From: Yi Sun <yi.sun@...soc.com>
To: <sunyibuaa@...il.com>, <tj@...nel.org>, <jiangshanlai@...il.com>,
        <jaegeuk@...nel.org>, <chao@...nel.org>
CC: <ebiggers@...gle.com>, <linux-f2fs-devel@...ts.sourceforge.net>,
        <linux-kernel@...r.kernel.org>, <kent.overstreet@...ux.dev>,
        <niuzhiguo84@...il.com>, <Hao_hao.Wang@...soc.com>,
        <yunlongxing23@...il.com>, <yi.sun@...soc.com>
Subject: [PATCH v2 0/2] new struct io_work and use it in f2fs fsverity work

Many works will go to submit_bio(). In many cases, the default
io priority of kworker cannot meet the real-time requirements of
the work. Such as f2fs_verify_bio work.

If a high-task-priority process reads the verity-file, it is
possible that the high-task-priority process will be slowly
because the kworker's io priority is too low.

A new work struct containing io priority can solve this problem.

Yi Sun (2):
  workqueue: new struct io_work
  f2fs: set io priority for fsverity work

 fs/f2fs/data.c            | 17 +++++++------
 fs/f2fs/f2fs.h            |  1 +
 fs/f2fs/verity.c          |  5 ++++
 include/linux/workqueue.h | 47 ++++++++++++++++++++++++++++++++++++
 kernel/workqueue.c        | 50 +++++++++++++++++++++++++++++++++++++++
 5 files changed, 113 insertions(+), 7 deletions(-)

-- 
2.25.1