linux-kernel - Re: [PATCH v3 3/3] blk-wbt: doc: Update the doc of the wbt_lat

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: <phu3rvr3gcok72z3g3tjxjgfzasfhv2qbevs7ydgzt7tc2kgmy@ocyvpumyjx3x>
Date: Mon, 28 Jul 2025 11:41:27 +0200
From: Jan Kara <jack@...e.cz>
To: Tang Yizhou <yizhou.tang@...pee.com>
Cc: axboe@...nel.dk, hch@....de, jack@...e.cz, linux-block@...r.kernel.org, 
	linux-kernel@...r.kernel.org, tangyeechou@...il.com
Subject: Re: [PATCH v3 3/3] blk-wbt: doc: Update the doc of the wbt_lat_usec
 interface

On Mon 28-07-25 01:39:59, Tang Yizhou wrote:
> From: Tang Yizhou <yizhou.tang@...pee.com>
> 
> The symbol wb_window_usec cannot be found. Update the doc to reflect the
> latest implementation, in other words, the debugfs interface
> 'curr_win_nsec'.
> 
> Signed-off-by: Tang Yizhou <yizhou.tang@...pee.com>

Looks good! Feel free to add:

Reviewed-by: Jan Kara <jack@...e.cz>

								Honza

> ---
>  Documentation/ABI/stable/sysfs-block | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
> index 4ba771b56b3b..a3cf841ebdff 100644
> --- a/Documentation/ABI/stable/sysfs-block
> +++ b/Documentation/ABI/stable/sysfs-block
> @@ -731,7 +731,7 @@ Contact:	linux-block@...r.kernel.org
>  Description:
>  		[RW] If the device is registered for writeback throttling, then
>  		this file shows the target minimum read latency. If this latency
> -		is exceeded in a given window of time (see wb_window_usec), then
> +		is exceeded in a given window of time (see curr_win_nsec), then
>  		the writeback throttling will start scaling back writes. Writing
>  		a value of '0' to this file disables the feature. Writing a
>  		value of '-1' to this file resets the value to the default
> -- 
> 2.25.1
> 
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR