From: Mateusz Guzik <mjguzik@gmail.com>
To: brauner@kernel.org
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH] fs: warn on dirty inode in writeback paired with I_WILL_FREE
Date: Wed, 10 Dec 2025 14:43:03 +0100 [thread overview]
Message-ID: <20251210134303.1310039-1-mjguzik@gmail.com> (raw)
This is in preparation for removing the flag down the road.
Signed-off-by: Mateusz Guzik <mjguzik@gmail.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
next reply other threads:[~2025-12-10 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 13:43 Mateusz Guzik [this message]
2025-12-11 1:45 ` [syzbot ci] Re: fs: warn on dirty inode in writeback paired with I_WILL_FREE syzbot ci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251210134303.1310039-1-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox