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: introduce f2fs_schedule_timeout()
Date: Mon, 24 Nov 2025 18:50:16 +0000 [thread overview]
Message-ID: <176401021675.42009.13430401093424290304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251111115229.1729729-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Nov 2025 19:52:28 +0800 you wrote:
> In f2fs retry logic, we will call f2fs_io_schedule_timeout() to sleep as
> uninterruptible state (waiting for IO) for a while, however, in several
> paths below, we are not blocked by IO:
> - f2fs_write_single_data_page() return -EAGAIN due to racing on cp_rwsem.
> - f2fs_quota_write() and __replace_atomic_write_block() failed due to
> no memory.
> - f2fs_flush_device_cache() failed to submit preflush command.
> - __issue_discard_cmd_range() sleeps periodically in between two in batch
> discard submissions.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: introduce f2fs_schedule_timeout()
(no matching commit)
- [f2fs-dev,2/2] f2fs: change default schedule timeout value
https://git.kernel.org/jaegeuk/f2fs/c/2f4c126cc08b
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:[~2025-11-24 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 11:52 [PATCH 1/2] f2fs: introduce f2fs_schedule_timeout() Chao Yu
2025-11-11 11:52 ` [PATCH 2/2] f2fs: change default schedule timeout value Chao Yu
2025-11-24 18:50 ` 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=176401021675.42009.13430401093424290304.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