mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chandradhar Kumar <chandradhar.2003@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	Baokun Li <libaokun@linux.alibaba.com>, Jan Kara <jack@suse.cz>,
	Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	Zhang Yi <yi.zhang@huawei.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Chandradhar Kumar <chandradhar.2003@gmail.com>,
	syzbot+f111db4cb2acd44eb2f4@syzkaller.appspotmail.com
Subject: [PATCH] ext4: wait for tail page commit in ext4_truncate_failed_write()
Date: Thu, 12 Nov 2026 18:18:32 +0530	[thread overview]
Message-ID: <20261112124835.114888-1-chandradhar.2003@gmail.com> (raw)

When a buffered write fails partially (e.g., due to a user page fault)
on an ext4 filesystem mounted in data=journal mode with blocksize <
PAGE_SIZE, ext4_journalled_write_end() invokes ext4_truncate_failed_write()
to discard newly allocated blocks beyond inode->i_size.

If the updated inode->i_size straddles a folio whose buffers are currently
being committed to the journal, truncate_inode_pages() attempts to
partially invalidate that folio via ext4_journalled_invalidate_folio().
Because JBD2 cannot unmap buffers belonging to a committing transaction
on a partial folio, journal_unmap_buffer() returns -EBUSY, triggering
the WARN_ON() in ext4_journalled_invalidate_folio().

Unlike the standard truncate path in ext4_truncate_down(),
ext4_truncate_failed_write() does not wait for the committing
transaction on the tail page to finish before truncating the page cache.
Export ext4_wait_for_tail_page_commit() and call it in
ext4_truncate_failed_write() when data=journal is enabled before
acquiring filemap_invalidate_lock() and calling truncate_inode_pages().

Fixes: 53e872681fed ("ext4: fix deadlock in journal_unmap_buffer()")
Reported-by: syzbot+f111db4cb2acd44eb2f4@syzkaller.appspotmail.com
Closes: https://syzbot.org/bug?extid=f111db4cb2acd44eb2f4
Signed-off-by: Chandradhar Kumar <chandradhar.2003@gmail.com>
---
 fs/ext4/ext4.h     | 1 +
 fs/ext4/inode.c    | 2 +-
 fs/ext4/truncate.h | 3 +++
 3 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index bf0325ecbec7..cc714d7b292c 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@ -3215,6 +3215,7 @@ int ext4_get_fc_inode_loc(struct super_block *sb, unsigned long ino,
 extern int ext4_inode_attach_jinode(struct inode *inode);
 extern int ext4_can_truncate(struct inode *inode);
 extern int ext4_truncate(struct inode *);
+extern void ext4_wait_for_tail_page_commit(struct inode *inode);
 extern int ext4_break_layouts(struct inode *);
 extern int ext4_truncate_page_cache_block_range(struct inode *inode,
 						loff_t start, loff_t end);
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index e3129353d4ed..366345981438 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -6819,7 +6819,7 @@ int ext4_sync_inode_metadata(struct inode *inode, struct writeback_control *wbc)
  * buffers that are attached to a folio straddling i_size and are undergoing
  * commit. In that case we have to wait for commit to finish and try again.
  */
-static void ext4_wait_for_tail_page_commit(struct inode *inode)
+void ext4_wait_for_tail_page_commit(struct inode *inode)
 {
 	unsigned offset;
 	journal_t *journal = EXT4_SB(inode->i_sb)->s_journal;
diff --git a/fs/ext4/truncate.h b/fs/ext4/truncate.h
index ce84aa2786c7..19ed4673284c 100644
--- a/fs/ext4/truncate.h
+++ b/fs/ext4/truncate.h
@@ -17,6 +17,9 @@ static inline void ext4_truncate_failed_write(struct inode *inode)
 	 * We don't need to call ext4_break_layouts() because the blocks we
 	 * are truncating were never visible to userspace.
 	 */
+	if (ext4_should_journal_data(inode))
+		ext4_wait_for_tail_page_commit(inode);
+
 	filemap_invalidate_lock(mapping);
 	truncate_inode_pages(mapping, inode->i_size);
 	ext4_truncate(inode);
-- 
2.56.0


                 reply	other threads:[~2026-11-12 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261112124835.114888-1-chandradhar.2003@gmail.com \
    --to=chandradhar.2003@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=syzbot+f111db4cb2acd44eb2f4@syzkaller.appspotmail.com \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.com \
    /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

all inboxes | Powered by JetHome®