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

Message-ID: <aH8osRbuecxTLur4@infradead.org>
Date: Mon, 21 Jul 2025 22:59:13 -0700
From: 'Christoph Hellwig' <hch@...radead.org>
To: hoyoung seo <hy50.seo@...sung.com>
Cc: 'Christoph Hellwig' <hch@...radead.org>, 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 05:37:03PM +0900, hoyoung seo wrote:
> No way..
> It's because i just don't know much about this part.
> And WQ_MEM_RECLAIM flag is absolutely necessary.

As a rule of thumb try to write an explanation why a change is safe.
That usually kicks of a process to think about the implications.