From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't break allocation when crossing contiguous sections
Date: Thu, 24 Jul 2025 20:30:08 +0000 [thread overview]
Message-ID: <175338900874.2519964.9616561185237270230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250721020231.2482090-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 21 Jul 2025 10:02:31 +0800 you wrote:
> Commit 0638a3197c19 ("f2fs: avoid unused block when dio write in LFS
> mode") has fixed unused block issue for dio write in lfs mode.
>
> However, f2fs_map_blocks() may break and return smaller extent when
> last allocated block locates in the end of section, even allocator
> can allocate contiguous blocks across sections.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't break allocation when crossing contiguous sections
https://git.kernel.org/jaegeuk/f2fs/c/f0a7adfedcc8
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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't break allocation when crossing contiguous sections
Date: Thu, 24 Jul 2025 20:30:08 +0000 [thread overview]
Message-ID: <175338900874.2519964.9616561185237270230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250721020231.2482090-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 21 Jul 2025 10:02:31 +0800 you wrote:
> Commit 0638a3197c19 ("f2fs: avoid unused block when dio write in LFS
> mode") has fixed unused block issue for dio write in lfs mode.
>
> However, f2fs_map_blocks() may break and return smaller extent when
> last allocated block locates in the end of section, even allocator
> can allocate contiguous blocks across sections.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't break allocation when crossing contiguous sections
https://git.kernel.org/jaegeuk/f2fs/c/f0a7adfedcc8
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:[~2025-07-24 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250721020241epcas2p1481962181d9f81f127e122736923fe20@epcms2p6>
2025-07-21 2:02 ` [f2fs-dev] [PATCH] f2fs: don't break allocation when crossing contiguous sections Chao Yu via Linux-f2fs-devel
2025-07-21 2:02 ` Chao Yu
2025-07-24 20:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-07-24 20:30 ` [f2fs-dev] " patchwork-bot+f2fs
2025-07-30 1:53 ` Daejun Park
2025-07-30 1:53 ` Daejun Park
2025-07-30 7:39 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-07-30 7:39 ` Chao Yu
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=175338900874.2519964.9616561185237270230.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.