From: Yun Zhou <yun.zhou@windriver.com>
To: <tytso@mit.edu>, <adilger.kernel@dilger.ca>,
<libaokun@linux.alibaba.com>, <jack@suse.cz>,
<ojaswin@linux.ibm.com>, <ritesh.list@gmail.com>,
<yi.zhang@huawei.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yun.zhou@windriver.com>
Subject: [RFC PATCH 7/9] ext4: remove DA convert path for regular file inline data
Date: Mon, 27 Jul 2026 18:54:39 +0800 [thread overview]
Message-ID: <20260727105441.3213095-8-yun.zhou@windriver.com> (raw)
In-Reply-To: <20260727105441.3213095-1-yun.zhou@windriver.com>
Replace ext4_da_convert_inline_data_to_extent() with
ext4_convert_inline_data() in the DA write path.
The DA convert function left a problematic intermediate state
(has_inline_data=true, MAY_INLINE_DATA=false) that caused races with
concurrent page_mkwrite: the racing thread would call filemap_flush()
which triggers writepages, but writepages rejects inodes with
has_inline_data set, leading to BUG_ON or WARN_ON.
Since the synchronous convert (ext4_convert_inline_data_nolock) only
allocates one block, the delayed allocation benefit (block contiguity)
is negligible for this single-block case.
With DA convert eliminated for regular files, the !MAY_INLINE_DATA
branch in ext4_convert_inline_data() is dead code and removed.
Remove ext4_da_convert_inline_data_to_extent().
Fixes: 7b4cc9787fe3 ("ext4: evict inline data when writing to memory map")
Reported-by: syzbot+d1da16f03614058fdc48@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d1da16f03614058fdc48
Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
---
fs/ext4/inline.c | 86 +-----------------------------------------------
1 file changed, 1 insertion(+), 85 deletions(-)
diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c
index ebbb9b29e3e1..009a4e058793 100644
--- a/fs/ext4/inline.c
+++ b/fs/ext4/inline.c
@@ -21,10 +21,6 @@
#define EXT4_INLINE_DOTDOT_OFFSET 2
#define EXT4_INLINE_DOTDOT_SIZE 4
-
-static int ext4_da_convert_inline_data_to_extent(struct address_space *mapping,
- struct inode *inode);
-
static int ext4_get_inline_size(struct inode *inode)
{
if (EXT4_I(inode)->i_inline_off)
@@ -538,76 +534,8 @@ int ext4_generic_write_inline_data(struct address_space *mapping,
struct folio **foliop,
bool da)
{
- int ret;
- int retries = 0;
-
/* Inline data is deprecated: always convert to block format */
- if (!da)
- return ext4_convert_inline_data(inode);
-
-retry:
- ret = ext4_da_convert_inline_data_to_extent(mapping, inode);
- if (ret == -ENOSPC && ext4_should_retry_alloc(inode->i_sb, &retries))
- goto retry;
- return ret;
-}
-
-/*
- * Try to make the page cache and handle ready for the inline data case.
- * We can call this function in 2 cases:
- * 1. The inode is created and the first write exceeds inline size. We can
- * clear the inode state safely.
- * 2. The inode has inline data, then we need to read the data, make it
- * update and dirty so that ext4_da_writepages can handle it. We don't
- * need to start the journal since the file's metadata isn't changed now.
- */
-static int ext4_da_convert_inline_data_to_extent(struct address_space *mapping,
- struct inode *inode)
-{
- int ret = 0, inline_size;
- struct folio *folio;
-
- folio = __filemap_get_folio(mapping, 0, FGP_WRITEBEGIN,
- mapping_gfp_mask(mapping));
- if (IS_ERR(folio))
- return PTR_ERR(folio);
-
- down_read(&EXT4_I(inode)->xattr_sem);
- if (!ext4_has_inline_data(inode)) {
- ext4_clear_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA);
- goto out;
- }
-
- inline_size = ext4_get_inline_size(inode);
-
- if (!folio_test_uptodate(folio)) {
- ret = ext4_read_inline_folio(inode, folio);
- if (ret < 0)
- goto out;
- }
-
- ret = ext4_block_write_begin(NULL, folio, 0, inline_size,
- ext4_da_get_block_prep);
- if (ret) {
- up_read(&EXT4_I(inode)->xattr_sem);
- folio_unlock(folio);
- folio_put(folio);
- ext4_truncate_failed_write(inode);
- return ret;
- }
-
- clear_buffer_new(folio_buffers(folio));
- folio_mark_dirty(folio);
- folio_mark_uptodate(folio);
- ext4_clear_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA);
-
-out:
- up_read(&EXT4_I(inode)->xattr_sem);
- if (folio) {
- folio_unlock(folio);
- folio_put(folio);
- }
- return ret;
+ return ext4_convert_inline_data(inode);
}
#ifdef INLINE_DIR_DEBUG
@@ -1650,18 +1578,6 @@ int ext4_convert_inline_data(struct inode *inode)
if (!ext4_has_inline_data(inode)) {
ext4_clear_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA);
return 0;
- } else if (!ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)) {
- /*
- * Inode has inline data but EXT4_STATE_MAY_INLINE_DATA is
- * cleared. This means we are in the middle of moving of
- * inline data to delay allocated block. Just force writeout
- * here to finish conversion.
- */
- error = filemap_flush(inode->i_mapping);
- if (error)
- return error;
- if (!ext4_has_inline_data(inode))
- return 0;
}
needed_blocks = ext4_chunk_trans_extent(inode, 1);
--
2.43.0
next prev parent reply other threads:[~2026-07-27 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 10:54 [RFC PATCH 0/9] ext4: phase out inline data write paths for regular files Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 1/9] ext4: add deprecation warning for inline_data feature Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 2/9] ext4: stop creating inline data for new regular files Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 3/9] ext4: use safe convert path for inline data write overflow Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 4/9] ext4: remove inline data write paths for regular files Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 5/9] ext4: remove dead inline data write code Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 6/9] ext4: allocate block before destroying inline data in conversion Yun Zhou
2026-07-27 10:54 ` Yun Zhou [this message]
2026-07-27 10:54 ` [RFC PATCH 8/9] ext4: document inline_data deprecation Yun Zhou
2026-07-27 10:54 ` [RFC PATCH 9/9] ext4: populate extent entry atomically during inline data destroy Yun Zhou
2026-07-27 15:03 ` [RFC PATCH 0/9] ext4: phase out inline data write paths for regular files Theodore Tso
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=20260727105441.3213095-8-yun.zhou@windriver.com \
--to=yun.zhou@windriver.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=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