From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
Nathan Chancellor <nathan@kernel.org>
Cc: 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 11:48:45 -0700 [thread overview]
Message-ID: <173402932544.982680.529127077152903218.b4-ty@kernel.dk> (raw)
In-Reply-To: <20241212-blk-iocost-fix-clamp-error-v1-1-b925491bc7d3@kernel.org>
On Thu, 12 Dec 2024 10:13:29 -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), \
> | ^
>
> [...]
Applied, thanks!
[1/1] blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
commit: 57e420c84f9ab55ba4c5e2ae9c5f6c8e1ea834d2
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-12-12 18:48 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
2024-12-12 18:48 ` Jens Axboe [this message]
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=173402932544.982680.529127077152903218.b4-ty@kernel.dk \
--to=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=nathan@kernel.org \
--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