linux-kernel - Re: [f2fs-dev] [PATCH 01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore

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 for Android: free password hash cracker in your pocket

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

Message-Id: 
 <176775661252.2218650.8734034218364835852.git-patchwork-notify@kernel.org>
Date: Wed, 07 Jan 2026 03:30:12 +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 01/14] f2fs: add lock elapsed time trace
 facility
 for f2fs rwsemphore

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.org>:

On Sun,  4 Jan 2026 10:07:16 +0800 you wrote:
> This patch adds lock elapsed time trace facility for f2fs rwsemphore.
> 
> If total elapsed time of critical region covered by lock exceeds a
> threshold, it will print tracepoint to dump information of lock related
> context, including:
> - thread information
> - CPU/IO priority
> - lock information
> - elapsed time
>  - total time
>  - running time (depend on CONFIG_64BIT)
>  - runnable time (depend on CONFIG_SCHED_INFO and CONFIG_SCHEDSTATS)
>  - io sleep time (depend on CONFIG_TASK_DELAY_ACCT and
> 		  /proc/sys/kernel/task_delayacct)
>  - other time    (by default other time will account nonio sleep time,
>                   but, if above kconfig is not defined, other time will
>                   include runnable time and/or io sleep time as wll)
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore
    https://git.kernel.org/jaegeuk/f2fs/c/79b3cebc70fc
  - [f2fs-dev,02/14] f2fs: sysfs: introduce max_lock_elapsed_time
    https://git.kernel.org/jaegeuk/f2fs/c/e4b75621fc43
  - [f2fs-dev,03/14] f2fs: trace elapsed time for cp_rwsem lock
    https://git.kernel.org/jaegeuk/f2fs/c/66e9e0d55d11
  - [f2fs-dev,04/14] f2fs: trace elapsed time for node_change lock
    https://git.kernel.org/jaegeuk/f2fs/c/f9f93602512b
  - [f2fs-dev,05/14] f2fs: trace elapsed time for node_write lock
    https://git.kernel.org/jaegeuk/f2fs/c/bb28b66875cc
  - [f2fs-dev,06/14] f2fs: trace elapsed time for gc_lock lock
    (no matching commit)
  - [f2fs-dev,07/14] f2fs: trace elapsed time for cp_global_sem lock
    https://git.kernel.org/jaegeuk/f2fs/c/ce9fe67c9cdb
  - [f2fs-dev,08/14] f2fs: trace elapsed time for io_rwsem lock
    https://git.kernel.org/jaegeuk/f2fs/c/67972c2b8974
  - [f2fs-dev,09/14] f2fs: clean up w/ __f2fs_schedule_timeout()
    https://git.kernel.org/jaegeuk/f2fs/c/b5da276ae6ab
  - [f2fs-dev,10/14] f2fs: fix to use jiffies based precision for DEFAULT_SCHEDULE_TIMEOUT
    https://git.kernel.org/jaegeuk/f2fs/c/da90b6715567
  - [f2fs-dev,11/14] f2fs: fix timeout precision of f2fs_io_schedule_timeout_killable()
    https://git.kernel.org/jaegeuk/f2fs/c/6fa116053951
  - [f2fs-dev,12/14] f2fs: rename FAULT_TIMEOUT to FAULT_ATOMIC_TIMEOUT
    https://git.kernel.org/jaegeuk/f2fs/c/7a127c80b0ee
  - [f2fs-dev,13/14] f2fs: introduce FAULT_LOCK_TIMEOUT
    https://git.kernel.org/jaegeuk/f2fs/c/c56254e2e042
  - [f2fs-dev,14/14] f2fs: sysfs: introduce inject_lock_timeout
    https://git.kernel.org/jaegeuk/f2fs/c/d36de29f4bb5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html