From: Yury Norov <yury.norov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Yoann Congal <yoann.congal@smile.fr>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Nhat Pham <nphamcs@gmail.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] gcc: disable '-Warray-bounds' for gcc-9
Date: Thu, 23 May 2024 13:09:30 -0700 [thread overview]
Message-ID: <Zk+ievkF4huCOtCt@yury-ThinkPad> (raw)
In-Reply-To: <20240523130026.c57a8e1e7f4140d2642c84d2@linux-foundation.org>
On Thu, May 23, 2024 at 01:00:26PM -0700, Andrew Morton wrote:
> On Wed, 22 May 2024 15:58:30 -0700 Yury Norov <yury.norov@gmail.com> wrote:
>
> > '-Warray-bounds' is already disabled for gcc-10+. Now that we've merged
> > bitmap_{read,write), I see the following error when building the kernel
> > with gcc-9.4 (Ubuntu 20.04.4 LTS) for x86_64 allmodconfig:
> >
> > drivers/pinctrl/pinctrl-cy8c95x0.c: In function ‘cy8c95x0_read_regs_mask.isra.0’:
> > include/linux/bitmap.h:756:18: error: array subscript [1, 288230376151711744] is outside array bounds of ‘long unsigned int[1]’ [-Werror=array-bounds]
> > 756 | value_high = map[index + 1] & BITMAP_LAST_WORD_MASK(start + nbits);
> > | ~~~^~~~~~~~~~~
> >
> > The immediate reason is that the commit b44759705f7d ("bitmap: make
> > bitmap_{get,set}_value8() use bitmap_{read,write}()") switched the
> > bitmap_get_value8() to an alias of bitmap_read(); the same for 'set'.
>
> So it seems that all kernels which contain b44759705f7d should have
> this change? If so, and as b44759705f7d appears to be in the net tree
> then the net tree is a suitable place to carry this patch?
>
> Or I can send it into Linus this -rc cycle and things will sort themselves out.
>
> Thoughts?
This is a real build breaker, so yes - I would like to have the fix in
this -rc. No preference regarding the tree.
prev parent reply other threads:[~2024-05-23 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:58 Yury Norov
2024-05-23 20:00 ` Andrew Morton
2024-05-23 20:09 ` Yury Norov [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=Zk+ievkF4huCOtCt@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nphamcs@gmail.com \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=yoann.congal@smile.fr \
/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
all inboxes | Powered by JetHome®