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 1/2] f2fs: fix to reclaim space in f2fs_allocate_pinning_section()
Date: Thu, 13 Aug 2026 16:01:09 +0000 [thread overview]
Message-ID: <178663686914.2934858.14952972896342801609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260812121756.278690-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 12 Aug 2026 12:17:54 +0000 you wrote:
> It needs to trigger checkpoint to free space reclaimed by f2fs_gc_range(),
> otherwise, fallocate() on pinfile will fail easily even there is slash
> space in conventional zone.
>
> [Testcase]
> nullblk_create.sh 512 2 1024 1024
> mkfs.f2fs /dev/nullb0 -f -m
> mount /dev/nullb0 /mnt/f2fs/
> touch /mnt/f2fs/pinfile
> f2fs_io pinfile set /mnt/f2fs/pinfile
> mkdir /mnt/f2fs/dir/
> for((i=0;i<3934;i++)) do { dd if=/dev/zero of=/mnt/f2fs/dir/$i bs=1M count=1;} done
> sync
> for((i=0;i<3934;i+=2)) do { rm /mnt/f2fs/dir/$i;} done
> for((i=0;i<1950;i++)) do { rm /mnt/f2fs/dir/$i;} done
> sync
> f2fs_io fallocate 0 0 $((1024*1024*1024)) /mnt/f2fs/pinfile
> sync
> stat /mnt/f2fs/pinfile
> f2fs_io fiemap 0 $((1024*1024*1024)) /mnt/f2fs/pinfile
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to reclaim space in f2fs_allocate_pinning_section()
https://git.kernel.org/jaegeuk/f2fs/c/5502c956d6f3
- [f2fs-dev,2/2] f2fs: fix to shrink gc_lock coverage in f2fs_gc_range()
https://git.kernel.org/jaegeuk/f2fs/c/a53894831f5d
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-08-13 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 12:17 Chao Yu
2026-08-12 12:17 ` [PATCH 2/2] f2fs: fix to shrink gc_lock coverage in f2fs_gc_range() Chao Yu
2026-08-13 16:01 ` 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=178663686914.2934858.14952972896342801609.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
all inboxes | Powered by JetHome®