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 1/2] f2fs: cache: pin cached block in f2fs_end_cache_writeback()
Date: Tue, 13 Oct 2026 22:30:13 +0000 [thread overview]
Message-ID: <179193061376.1493834.1008667944485140463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930235435.3789910-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 30 Sep 2026 23:54:34 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> Like page cache folios, writeback does not hold an active reference on
> the cached block during I/O flight, relying instead on truncation or
> shrinker callers to wait on F2FS_BLOCK_WRITEBACK before releasing the entry.
>
> However, in f2fs_end_cache_writeback(), clear_and_wake_up_bit() executes
> two distinct steps:
> 1. clear_bit_unlock(F2FS_BLOCK_WRITEBACK, &entry->state): clears the bit.
> 2. wake_up_bit(&entry->state, F2FS_BLOCK_WRITEBACK): hashes &entry->state
> to look up the waitqueue and wakes waiting tasks.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: cache: pin cached block in f2fs_end_cache_writeback()
https://git.kernel.org/jaegeuk/f2fs/c/6e392158cf54
- [f2fs-dev,2/2] f2fs: cache: pin cached block in f2fs_unlock_cache()
https://git.kernel.org/jaegeuk/f2fs/c/61ba87b33e87
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-10-13 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 23:54 Chao Yu
2026-09-30 23:54 ` [PATCH 2/2] f2fs: cache: pin cached block in f2fs_unlock_cache() Chao Yu
2026-10-13 22: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=179193061376.1493834.1008667944485140463.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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®