Linux block layer
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: Josef Bacik <josef@toxicpanda.com>, Jens Axboe <axboe@kernel.dk>,
	cgroups@vger.kernel.org, linux-block@vger.kernel.org,
	llvm@lists.linux.dev, patches@lists.linux.dev,
	David Laight <david.laight@aculab.com>,
	Linux Kernel Functional Testing <lkft@linaro.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
Date: Thu, 12 Dec 2024 10:44:44 -0700	[thread overview]
Message-ID: <20241212174444.GB2149156@ax162> (raw)
In-Reply-To: <Z1sbG2zh8xmb-lxu@slm.duckdns.org>

On Thu, Dec 12, 2024 at 07:19:23AM -1000, Tejun Heo wrote:
> On Thu, Dec 12, 2024 at 10:13:29AM -0700, Nathan Chancellor wrote:
> > After a recent change to clamp() and its variants [1] that increases the
> > coverage of the check that high is greater than low because it can be
> > done through inlining, certain build configurations (such as s390
> > defconfig) fail to build with clang with:
> > 
> >   block/blk-iocost.c:1101:11: error: call to '__compiletime_assert_557' declared with 'error' attribute: clamp() low limit 1 greater than high limit active
> >    1101 |                 inuse = clamp_t(u32, inuse, 1, active);
> >         |                         ^
> >   include/linux/minmax.h:218:36: note: expanded from macro 'clamp_t'
> >     218 | #define clamp_t(type, val, lo, hi) __careful_clamp(type, val, lo, hi)
> >         |                                    ^
> >   include/linux/minmax.h:195:2: note: expanded from macro '__careful_clamp'
> >     195 |         __clamp_once(type, val, lo, hi, __UNIQUE_ID(v_), __UNIQUE_ID(l_), __UNIQUE_ID(h_))
> >         |         ^
> >   include/linux/minmax.h:188:2: note: expanded from macro '__clamp_once'
> >     188 |         BUILD_BUG_ON_MSG(statically_true(ulo > uhi),                            \
> >         |         ^
> > 
> > __propagate_weights() is called with an active value of zero in
> > ioc_check_iocgs(), which results in the high value being less than the
> > low value, which is undefined because the value returned depends on the
> > order of the comparisons.
> > 
> > The purpose of this expression is to ensure inuse is not more than
> > active and at least 1. This could be written more simply with a ternary
> > expression that uses min(inuse, active) as the condition so that the
> > value of that condition can be used if it is not zero and one if it is.
> > Do this conversion to resolve the error and add a comment to deter
> > people from turning this back into clamp().
> > 
> > Link: https://lore.kernel.org/r/34d53778977747f19cce2abb287bb3e6@AcuMS.aculab.com/ [1]
> > Suggested-by: David Laight <david.laight@aculab.com>
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > Closes: https://lore.kernel.org/llvm/CA+G9fYsD7mw13wredcZn0L-KBA3yeoVSTuxnss-AEWMN3ha0cA@mail.gmail.com/
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202412120322.3GfVe3vF-lkp@intel.com/
> > Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> 
> Acked-by: Tejun Heo <tj@kernel.org>

Thanks for the quick response!

> This likely deserves:
> 
> Fixes: 7caa47151ab2 ("blkcg: implement blk-iocost")
> Cc: stable@vger.kernel.org # v5.4+

Thanks, I was wondering if I should have provided those. I'll carry them
forward on any future revisions, as I assume Jens can pick those up with
your tag if this is good enough.

> 
> -- 
> tejun
> 

  parent reply	other threads:[~2024-12-12 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 17:13 [PATCH] blk-iocost: Avoid using clamp() on inuse in __propagate_weights() Nathan Chancellor
2024-12-12 17:19 ` Tejun Heo
2024-12-12 17:28   ` David Laight
2024-12-12 17:44   ` Nathan Chancellor [this message]
2024-12-12 18:48 ` Jens Axboe

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=20241212174444.GB2149156@ax162 \
    --to=nathan@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=david.laight@aculab.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=lkft@linaro.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=patches@lists.linux.dev \
    --cc=tj@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