From: Baokun Li <libaokun1@huawei.com>
To: Zhang Yi <yi.zhang@huaweicloud.com>, <linux-ext4@vger.kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tytso@mit.edu>, <adilger.kernel@dilger.ca>, <jack@suse.cz>,
<ojaswin@linux.ibm.com>, <ritesh.list@gmail.com>,
<yi.zhang@huawei.com>, <yizhang089@gmail.com>,
<yangerkun@huawei.com>, <yukuai@fnnas.com>
Subject: Re: [PATCH -next v2 6/7] ext4: simply the mapping query logic in ext4_iomap_begin()
Date: Wed, 31 Dec 2025 15:46:14 +0800 [thread overview]
Message-ID: <65ffdc21-1f94-428c-be06-f81c87f019bc@huawei.com> (raw)
In-Reply-To: <20251223011802.31238-7-yi.zhang@huaweicloud.com>
On 2025-12-23 09:18, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
>
> In the write path mapping check of ext4_iomap_begin(), the return value
> 'ret' should never greater than orig_mlen. If 'ret' equals 'orig_mlen',
> it can be returned directly without checking IOMAP_ATOMIC.
>
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
Looks good. Feel free to add:
Reviewed-by: Baokun Li <libaokun1@huawei.com>
> ---
> fs/ext4/inode.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index b84a2a10dfb8..67fe7d0f47e3 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -3816,17 +3816,19 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
> if (offset + length <= i_size_read(inode)) {
> ret = ext4_map_blocks(NULL, inode, &map, 0);
> /*
> - * For atomic writes the entire requested length should
> - * be mapped. For DAX we convert extents to initialized
> - * ones before copying the data, otherwise we do it
> - * after I/O so there's no need to call into
> - * ext4_iomap_alloc().
> + * For DAX we convert extents to initialized ones before
> + * copying the data, otherwise we do it after I/O so
> + * there's no need to call into ext4_iomap_alloc().
> */
> if ((map.m_flags & EXT4_MAP_MAPPED) ||
> (!(flags & IOMAP_DAX) &&
> (map.m_flags & EXT4_MAP_UNWRITTEN))) {
> - if ((!(flags & IOMAP_ATOMIC) && ret > 0) ||
> - (flags & IOMAP_ATOMIC && ret >= orig_mlen))
> + /*
> + * For atomic writes the entire requested
> + * length should be mapped.
> + */
> + if (ret == orig_mlen ||
> + (!(flags & IOMAP_ATOMIC) && ret > 0))
> goto out;
> }
> map.m_len = orig_mlen;
next prev parent reply other threads:[~2025-12-31 7:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 1:17 [PATCH -next v2 0/7] ext4: defer unwritten splitting until I/O completion Zhang Yi
2025-12-23 1:17 ` [PATCH -next v2 1/7] ext4: use reserved metadata blocks when splitting extent on endio Zhang Yi
2025-12-31 7:34 ` Baokun Li
2026-01-03 13:42 ` Ojaswin Mujoo
2026-01-05 1:17 ` Zhang Yi
2025-12-23 1:17 ` [PATCH -next v2 2/7] ext4: don't split extent before submitting I/O Zhang Yi
2025-12-31 7:35 ` Baokun Li
2026-01-03 13:47 ` Ojaswin Mujoo
2025-12-23 1:17 ` [PATCH -next v2 3/7] ext4: avoid starting handle when dio writing an unwritten extent Zhang Yi
2025-12-31 7:36 ` Baokun Li
2026-01-03 14:06 ` Ojaswin Mujoo
2025-12-23 1:17 ` [PATCH -next v2 4/7] ext4: remove useless ext4_iomap_overwrite_ops Zhang Yi
2025-12-31 7:40 ` Baokun Li
2026-01-03 14:14 ` Ojaswin Mujoo
2025-12-23 1:18 ` [PATCH -next v2 5/7] ext4: remove unused unwritten parameter in ext4_dio_write_iter() Zhang Yi
2025-12-31 7:42 ` Baokun Li
2026-01-03 14:16 ` Ojaswin Mujoo
2025-12-23 1:18 ` [PATCH -next v2 6/7] ext4: simply the mapping query logic in ext4_iomap_begin() Zhang Yi
2025-12-31 7:46 ` Baokun Li [this message]
2026-01-03 14:17 ` Ojaswin Mujoo
2026-01-04 13:00 ` Markus Elfring
2026-01-05 1:18 ` Zhang Yi
2025-12-23 1:18 ` [PATCH -next v2 7/7] ext4: remove EXT4_GET_BLOCKS_IO_CREATE_EXT Zhang Yi
2025-12-31 7:55 ` Baokun Li
2026-01-03 14:20 ` Ojaswin Mujoo
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=65ffdc21-1f94-428c-be06-f81c87f019bc@huawei.com \
--to=libaokun1@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yizhang089@gmail.com \
--cc=yukuai@fnnas.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®