From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Yury Norov <yury.norov@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Qian Cai <quic_qiancai@quicinc.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitmap: simplify GENMASK(size - 1, 0) lines
Date: Tue, 26 Oct 2021 22:42:41 +0300 [thread overview]
Message-ID: <YXhaMVTymVNzOlGT@smile.fi.intel.com> (raw)
In-Reply-To: <YXhW8K7DxadyVgx3@yury-ThinkPad>
+Cc: Greg (see below)
On Tue, Oct 26, 2021 at 12:28:48PM -0700, Yury Norov wrote:
> On Tue, Oct 26, 2021 at 10:21:58PM +0300, Andy Shevchenko wrote:
> > On Tue, Oct 26, 2021 at 11:54:16AM -0700, Yury Norov wrote:
> > > On Tue, Oct 26, 2021 at 10:41:08AM -0400, Qian Cai wrote:
> > > > Since "size" is an "unsigned int", the rvalue "size - 1" will still be
> > > > "unsigned int" according to the C standard (3.2.1.5 Usual arithmetic
> > > > conversions). Therefore, GENMASK(size - 1, 0) will always return 0UL. Those
> > > > are also caught by GCC (W=2):
> > > >
> > > > ./include/linux/find.h: In function 'find_first_bit':
> > > > ./include/linux/bits.h:25:22: warning: comparison of unsigned expression in '< 0' is always false [-Wtype-limits]
> > > > 25 | __is_constexpr((l) > (h)), (l) > (h), 0)))
> > > > | ^
> > > > ./include/linux/build_bug.h:16:62: note: in definition of macro 'BUILD_BUG_ON_ZERO'
> > > > 16 | #define BUILD_BUG_ON_ZERO(e) ((int)(sizeof(struct { int:(-!!(e)); })))
> > > > | ^
> > > > ./include/linux/bits.h:25:3: note: in expansion of macro '__is_constexpr'
> > > > 25 | __is_constexpr((l) > (h)), (l) > (h), 0)))
> > > > | ^~~~~~~~~~~~~~
> > > > ./include/linux/bits.h:38:3: note: in expansion of macro 'GENMASK_INPUT_CHECK'
> > > > 38 | (GENMASK_INPUT_CHECK(h, l) + __GENMASK(h, l))
> > > > | ^~~~~~~~~~~~~~~~~~~
> > > > ./include/linux/find.h:119:31: note: in expansion of macro 'GENMASK'
> > > > 119 | unsigned long val = *addr & GENMASK(size - 1, 0);
> > > > | ^~~~~~~
> > > > ./include/linux/bits.h:25:34: warning: comparison of unsigned expression in '< 0' is always false [-Wtype-limits]
> > > > 25 | __is_constexpr((l) > (h)), (l) > (h), 0)))
> > > > | ^
> > > > ./include/linux/build_bug.h:16:62: note: in definition of macro 'BUILD_BUG_ON_ZERO'
> > > > 16 | #define BUILD_BUG_ON_ZERO(e) ((int)(sizeof(struct { int:(-!!(e)); })))
> > > > | ^
> > > > ./include/linux/bits.h:38:3: note: in expansion of macro 'GENMASK_INPUT_CHECK'
> > > > 38 | (GENMASK_INPUT_CHECK(h, l) + __GENMASK(h, l))
> > > > | ^~~~~~~~~~~~~~~~~~~
> > > > ./include/linux/find.h:119:31: note: in expansion of macro 'GENMASK'
> > > > 119 | unsigned long val = *addr & GENMASK(size - 1, 0);
> > > > | ^~~~~~~
> > > >
> > > > Signed-off-by: Qian Cai <quic_qiancai@quicinc.com>
> > > > ---
> > > > include/linux/find.h | 28 ++++++++--------------------
> > > > 1 file changed, 8 insertions(+), 20 deletions(-)
> > > >
> > > > diff --git a/include/linux/find.h b/include/linux/find.h
> > > > index 5bb6db213bcb..5ce2b17aea42 100644
> > > > --- a/include/linux/find.h
> > > > +++ b/include/linux/find.h
> > > > @@ -115,11 +115,8 @@ unsigned long find_next_zero_bit(const unsigned long *addr, unsigned long size,
> > > > static inline
> > > > unsigned long find_first_bit(const unsigned long *addr, unsigned long size)
> > > > {
> > > > - if (small_const_nbits(size)) {
> > > > - unsigned long val = *addr & GENMASK(size - 1, 0);
> > > > -
> > > > - return val ? __ffs(val) : size;
> > > > - }
> > > > + if (small_const_nbits(size))
> > > > + return size;
> > > >
> > > > return _find_first_bit(addr, size);
> > > > }
> > >
> > > [...]
> > >
> > > Nice catch! I'm a bit concerned that small_const_nbits() will never
> > > allow GENMASK() to be passed with size == 0, but the patch looks
> > > good to me overall.
> >
> > Can you explain to me how it is supposed to work?
> >
> > For example,
> >
> > x = 0xaa55;
> > size = 5;
> >
> > printf("%lu\n", find_first_bit(&x, size));
> >
> > In the resulting code we will always have 5 as the result,
> > but is it correct one?
>
> I think it would work really bad and fail to load the kernel
> for many systems, especially those with NR_CPUS == 64 or less.
>
> That's why I think Apr 1 branch is a good place for it.
Ah, I have got you. We are on the same page then.
Now, I have checked that email appearance in the upstream:
$ git log --oneline --author="quic_qiancai@quicinc.com"
95cadae320be fortify: strlen: Avoid shadowing previous locals
94560f6156fe Revert "arm pl011 serial: support multi-irq request"
While first one perhaps okay, although it also refers to W=2,
I have now doubts if the "Revert" was really thought through
and not just yet another UMN-like experiment.
Greg, what do you think is the best course of actions here?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-10-26 19:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:41 [PATCH] bitmap: simplify GENMASK(size - 1, 0) lines Qian Cai
2021-10-26 15:10 ` Andy Shevchenko
2021-10-26 15:26 ` Qian Cai
2021-10-26 18:54 ` Yury Norov
2021-10-26 19:21 ` Andy Shevchenko
2021-10-26 19:28 ` Yury Norov
2021-10-26 19:42 ` Andy Shevchenko [this message]
2021-10-26 19:54 ` Qian Cai
2021-10-27 9:44 ` Andy Shevchenko
2021-10-27 15:06 ` Qian Cai
2021-10-26 19:33 ` Qian Cai
2021-10-27 9:34 ` Andy Shevchenko
2021-10-29 1:36 ` [bitmap] ca95e676a1: BUG:unable_to_handle_page_fault_for_address kernel test robot
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=YXhaMVTymVNzOlGT@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=quic_qiancai@quicinc.com \
--cc=yury.norov@gmail.com \
/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