From: Kees Cook <keescook@chromium.org>
To: Marco Elver <elver@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
linux-pci <linux-pci@vger.kernel.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Andrey Ryabinin" <ryabinin.a.a@gmail.com>,
"Stan Skowronek" <stan@corellium.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Helge Deller" <deller@gmx.de>,
kasan-dev <kasan-dev@googlegroups.com>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Anton Altaparmakov" <anton@tuxera.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"Nick Terrell" <terrelln@fb.com>,
"Joey Gouly" <joey.gouly@arm.com>,
"André Almeida" <andrealmeid@collabora.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Parisc List" <linux-parisc@vger.kernel.org>,
linux-ntfs-dev@lists.sourceforge.net,
"Hector Martin" <marcan@marcan.st>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Rob Clark" <robdclark@gmail.com>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Build regressions/improvements in v5.16-rc1
Date: Mon, 15 Nov 2021 16:35:14 -0800 [thread overview]
Message-ID: <202111151633.DE719CE@keescook> (raw)
In-Reply-To: <YZKOce4XhAU49+Yn@elver.google.com>
On Mon, Nov 15, 2021 at 05:44:33PM +0100, Marco Elver wrote:
> On Mon, Nov 15, 2021 at 05:12PM +0100, Geert Uytterhoeven wrote:
> [...]
> > > + /kisskb/src/include/linux/fortify-string.h: error: call to '__read_overflow' declared with attribute error: detected read beyond size of object (1st parameter): => 263:25, 277:17
> >
> > in lib/test_kasan.c
> >
> > s390-all{mod,yes}config
> > arm64-allmodconfig (gcc11)
>
> Kees, wasn't that what [1] was meant to fix?
> [1] https://lkml.kernel.org/r/20211006181544.1670992-1-keescook@chromium.org
Ah, I found it:
http://kisskb.ellerman.id.au/kisskb/buildresult/14660585/log/
it's actually:
inlined from 'kasan_memcmp' at /kisskb/src/lib/test_kasan.c:897:2:
and
inlined from 'kasan_memchr' at /kisskb/src/lib/test_kasan.c:872:2:
I can send a patch doing the same as what [1] does for these cases too.
--
Kees Cook
next prev parent reply other threads:[~2021-11-16 0:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211115155105.3797527-1-geert@linux-m68k.org>
2021-11-15 16:12 ` Build regressions/improvements in v5.16-rc1 Geert Uytterhoeven
2021-11-15 16:44 ` Marco Elver
2021-11-16 0:31 ` Kees Cook
2021-11-16 0:35 ` Kees Cook [this message]
2021-11-15 16:44 ` Helge Deller
2021-11-16 21:08 ` Nick Terrell
2021-11-16 21:27 ` Nick Terrell
2021-11-17 1:59 ` Nick Terrell
2021-11-17 2:05 ` Randy Dunlap
2021-11-17 2:19 ` Nick Terrell
2021-11-17 8:24 ` Geert Uytterhoeven
2021-11-17 11:22 ` Helge Deller
2021-11-17 19:39 ` Nick Terrell
2021-11-16 9:15 ` Thomas Bogendoerfer
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=202111151633.DE719CE@keescook \
--to=keescook@chromium.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andrealmeid@collabora.com \
--cc=anton@tuxera.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=elver@google.com \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=joey.gouly@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marcan@marcan.st \
--cc=peterz@infradead.org \
--cc=robdclark@gmail.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sergio.paracuellos@gmail.com \
--cc=stan@corellium.com \
--cc=terrelln@fb.com \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).