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: <171711994168.606218.16094424745811206145.b4-ty@kernel.dk>
Date: Thu, 30 May 2024 19:45:41 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Tejun Heo <tj@...nel.org>, Josef Bacik <josef@...icpanda.com>, 
 Waiman Long <longman@...hat.com>
Cc: cgroups@...r.kernel.org, linux-block@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Dan Schatzberg <schatzberg.dan@...il.com>, 
 Ming Lei <ming.lei@...hat.com>, Justin Forbes <jforbes@...hat.com>
Subject: Re: [PATCH] blk-throttle: Fix incorrect display of io.max


On Thu, 30 May 2024 09:45:47 -0400, Waiman Long wrote:
> Commit bf20ab538c81 ("blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW")
> attempts to revert the code change introduced by commit cd5ab1b0fcb4
> ("blk-throttle: add .low interface").  However, it leaves behind the
> bps_conf[] and iops_conf[] fields in the throtl_grp structure which
> aren't set anywhere in the new blk-throttle.c code but are still being
> used by tg_prfill_limit() to display the limits in io.max. Now io.max
> always displays the following values if a block queue is used:
> 
> [...]

Applied, thanks!

[1/1] blk-throttle: Fix incorrect display of io.max
      commit: 0a751df4566c86e5a24f2a03290dad3d0f215692

Best regards,
-- 
Jens Axboe




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ