linux-kernel - Re: [PATCH v1] writback: remove WQ_MEM_RECLAIM flag in bdi

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]

Message-ID: <aH3on5GBd6AfgJuw@infradead.org>
Date: Mon, 21 Jul 2025 00:13:35 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "hy50.seo" <hy50.seo@...sung.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	alim.akhtar@...sung.com, avri.altman@....com, jejb@...ux.ibm.com,
	martin.petersen@...cle.com, beanhuo@...ron.com, bvanassche@....org,
	kwangwon.min@...sung.com, kwmad.kim@...sung.com, cpgs@...sung.com,
	h10.kim@...sung.com, willdeacon@...gle.com, jaegeuk@...gle.com,
	chao@...nel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v1] writback: remove WQ_MEM_RECLAIM flag in bdi_wq

On Mon, Jul 21, 2025 at 03:40:24PM +0900, hy50.seo wrote:
> if it write with the write back option with f2fs, kernel panic occurs.
> Because the write back function uses bdi_wq and WQ_MEM_RECLAIM flag
> is included and created.
> However, this function calls f2fs_do_quota() of f2fs and finally tries to
> perform quota_release_work.
> the quota_release_work is performed in the events_unbound workqueue,
> but the WQ_MEM_RECLAIM flag is not included.

And what makes you assume the WQ_MEM_RECLAIM was added just for fun
and can simply be deleted?