From: patchwork-bot+f2fs@kernel.org
To: Xiuhong Wang <xiuhong.wang@unisoc.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
xiuhong.wang.cn@gmail.com, hao_hao.wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix fiemap failure issue when page size is 16KB
Date: Thu, 07 Nov 2024 20:30:41 +0000 [thread overview]
Message-ID: <173101144199.2084993.6672876155571562205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241029061535.2676673-1-xiuhong.wang@unisoc.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 29 Oct 2024 14:15:35 +0800 you wrote:
> After enable 16K page size, an infinite loop may occur in
> fiemap (fm_length=UINT64_MAX) on a file, such as the 16KB
> scratch.img during the remount operation in Android.
>
> The condition for whether fiemap continues to map is to check
> whether the number of bytes corresponding to the next map.m_lblk
> exceeds blks_to_bytes(inode,max_inode_blocks(inode)) if there are HOLE.
> The latter does not take into account the maximum size of a file with 16KB
> page size, so the loop cannot be jumped out.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix fiemap failure issue when page size is 16KB
https://git.kernel.org/jaegeuk/f2fs/c/a7a7c1d423a6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-07 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 6:15 [PATCH] f2fs: fix fiemap failure issue when page size is 16KB Xiuhong Wang
2024-11-04 3:42 ` Chao Yu
2024-11-07 20:30 ` patchwork-bot+f2fs [this message]
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=173101144199.2084993.6672876155571562205.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=hao_hao.wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xiuhong.wang.cn@gmail.com \
--cc=xiuhong.wang@unisoc.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