From: patchwork-bot+f2fs@kernel.org
To: Daejun Park <daejun7.park@samsung.com>
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, nayeoni.kim@samsung.com,
siu.jung@samsung.com, sukka.kim@samsung.com,
dongjin_.kim@samsung.com
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: avoid unused block when dio write in LFS mode
Date: Mon, 16 Sep 2024 21:30:41 +0000 [thread overview]
Message-ID: <172652224174.3820990.5790897572991749927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240905052433epcms2p1dac78dff43776cc158bac5ae9d118160@epcms2p1>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 05 Sep 2024 14:24:33 +0900 you wrote:
> This patch addresses the problem that when using LFS mode, unused blocks
> may occur in f2fs_map_blocks() during block allocation for dio writes.
>
> If a new section is allocated during block allocation, it will not be
> included in the map struct by map_is_mergeable() if the LBA of the
> allocated block is not contiguous. However, the block already allocated
> in this process will remain unused due to the LFS mode.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: avoid unused block when dio write in LFS mode
https://git.kernel.org/jaegeuk/f2fs/c/0638a3197c19
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-09-16 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240905052433epcms2p1dac78dff43776cc158bac5ae9d118160@epcms2p1>
2024-09-05 5:24 ` [PATCH v2] f2fs: avoid unused block when dio write in LFS mode Daejun Park
2024-09-05 6:43 ` Chao Yu
2024-09-16 21: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=172652224174.3820990.5790897572991749927.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nayeoni.kim@samsung.com \
--cc=siu.jung@samsung.com \
--cc=sukka.kim@samsung.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