From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid potential section-unaligned pinfile
Date: Tue, 14 Jul 2026 03:00:07 +0000 [thread overview]
Message-ID: <178399800738.2939750.5347430287438781500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260629114918.224537-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 29 Jun 2026 11:49:18 +0000 you wrote:
> Blocks of pinfile may not aligned to section size due to wrong use
> on pinfile, result in heavy overhead of GC, let avoid this by
> adding additional check condition in f2fs_setattr().
>
> - truncate -s 8mb pinfile
> : random checkpoint may persist filesize w/ inode
> - fallocate -o 0 -l 8mb pinfile
> - f2fs_fallocate
> - f2fs_expand_inode_data
> - f2fs_allocate_pinning_section
> - f2fs_map_blocks
> - f2fs_map_lock
> - __allocate_data_block
> - file_need_truncate
> : w/ FADVISE_TRUNC_BIT, we can expect unaligned mapping can be
> truncated while open() if f2fs is not umount abnormally
> - f2fs_map_unlock
> : following f2fs checkpoint and sudden power-cut
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid potential section-unaligned pinfile
https://git.kernel.org/jaegeuk/f2fs/c/bf4272cef5ec
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:[~2026-07-14 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 11:49 Chao Yu
2026-06-30 8:50 ` [f2fs-dev] " Zhiguo Niu
2026-06-30 11:02 ` Chao Yu
2026-07-01 3:26 ` Zhiguo Niu
2026-07-02 14:26 ` Jaegeuk Kim
2026-07-03 0:17 ` Chao Yu
2026-07-14 3:00 ` 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=178399800738.2939750.5347430287438781500.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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