From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Sunmin Jeong <s_min.jeong@samsung.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
sj1557.seo@samsung.com
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to round down start offset of fallocate for pin file
Date: Mon, 22 Jun 2026 20:00:26 +0000 [thread overview]
Message-ID: <178215842604.1396481.3503226882368736427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260622052817.3972188-1-s_min.jeong@samsung.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 22 Jun 2026 14:28:17 +0900 you wrote:
> Currently, the length of fallocate for pin file is section-aligned to
> keep allocated sections from being selected as victims of GC. However,
> for the case that the start offset of fallocate is not aligned in
> section, the allocated sections can't be fully utilized. It's because a
> new section is allocated by f2fs_allocate_pinning_section() after using
> blks_per_sec blocks regardless of the start offset. As a result, several
> unexpected dirty segments may be created, including blocks assigned to
> the pinned file.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to round down start offset of fallocate for pin file
https://git.kernel.org/jaegeuk/f2fs/c/d2134b45eede
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Sunmin Jeong <s_min.jeong@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, sj1557.seo@samsung.com,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to round down start offset of fallocate for pin file
Date: Mon, 22 Jun 2026 20:00:26 +0000 [thread overview]
Message-ID: <178215842604.1396481.3503226882368736427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260622052817.3972188-1-s_min.jeong@samsung.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 22 Jun 2026 14:28:17 +0900 you wrote:
> Currently, the length of fallocate for pin file is section-aligned to
> keep allocated sections from being selected as victims of GC. However,
> for the case that the start offset of fallocate is not aligned in
> section, the allocated sections can't be fully utilized. It's because a
> new section is allocated by f2fs_allocate_pinning_section() after using
> blks_per_sec blocks regardless of the start offset. As a result, several
> unexpected dirty segments may be created, including blocks assigned to
> the pinned file.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to round down start offset of fallocate for pin file
https://git.kernel.org/jaegeuk/f2fs/c/d2134b45eede
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-22 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260622052831epcas1p205548491ce904c0cfda685ed05fe7cab@epcas1p2.samsung.com>
2026-06-22 5:28 ` [PATCH v2] f2fs: fix to round down start offset of fallocate for pin file Sunmin Jeong
2026-06-22 5:28 ` [f2fs-dev] " Sunmin Jeong
2026-06-22 12:41 ` Chao Yu via Linux-f2fs-devel
2026-06-22 12:41 ` Chao Yu
2026-06-22 20:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2026-06-22 20:00 ` [f2fs-dev] " patchwork-bot+f2fs
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=178215842604.1396481.3503226882368736427.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=s_min.jeong@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.