linux-kernel - Re: [f2fs-dev] [PATCH 1/2] f2fs: introduce f2fs_schedule

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176401021675.42009.13430401093424290304.git-patchwork-notify@kernel.org>
Date: Mon, 24 Nov 2025 18:50:16 +0000
From: patchwork-bot+f2fs@...nel.org
To: Chao Yu <chao@...nel.org>
Cc: jaegeuk@...nel.org, linux-kernel@...r.kernel.org,
 linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: introduce f2fs_schedule_timeout()

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.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