linux-kernel - [PATCH] fs: warn on dirty inode in writeback paired with I_WILL

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

Message-ID: <20251210134303.1310039-1-mjguzik@gmail.com>
Date: Wed, 10 Dec 2025 14:43:03 +0100
From: Mateusz Guzik <mjguzik@...il.com>
To: brauner@...nel.org
Cc: viro@...iv.linux.org.uk,
	jack@...e.cz,
	linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org,
	Mateusz Guzik <mjguzik@...il.com>
Subject: [PATCH] fs: warn on dirty inode in writeback paired with I_WILL_FREE

This is in preparation for removing the flag down the road.

Signed-off-by: Mateusz Guzik <mjguzik@...il.com>
---
 fs/fs-writeback.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index 6800886c4d10..633537003b88 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -1866,6 +1866,8 @@ static int writeback_single_inode(struct inode *inode,
 	 * as it can be finally deleted at this moment.
 	 */
 	if (!(inode_state_read(inode) & I_FREEING)) {
+		if (inode_state_read(inode) & I_WILL_FREE)
+			WARN_ON_ONCE(inode_state_read(inode) & I_DIRTY_ALL);
 		/*
 		 * If the inode is now fully clean, then it can be safely
 		 * removed from its writeback list (if any). Otherwise the
-- 
2.48.1