linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-s390@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.2-rc4
Date: Mon, 16 Jan 2023 13:36:34 +0100 (CET)	[thread overview]
Message-ID: <46ba7912-3df6-dff9-792-49f4eaadefec@linux-m68k.org> (raw)
In-Reply-To: <20230116122924.116745-1-geert@linux-m68k.org>

On Mon, 16 Jan 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.2-rc4[1] to v6.2-rc3-8-g1fe4fd6f5cad346e[3], the summaries are:
>  - build errors: +1/-5

   + /kisskb/src/include/linux/fortify-string.h: error: '__builtin_memcpy' reading 128 bytes from a region of size 0 [-Werror=stringop-overread]:  => 57:33

s390x-gcc11/s390-allmodconfig

/kisskb/src/arch/s390/kernel/setup.c: In function 'setup_lowcore_dat_on':
/kisskb/src/include/linux/fortify-string.h:57:33: error: '__builtin_memcpy' reading 128 bytes from a region of size 0 [-Werror=stringop-overread]
    57 | #define __underlying_memcpy     __builtin_memcpy
       |                                 ^
/kisskb/src/include/linux/fortify-string.h:578:9: note: in expansion of macro '__underlying_memcpy'
   578 |         __underlying_##op(p, q, __fortify_size);                        \
       |         ^~~~~~~~~~~~~
/kisskb/src/include/linux/fortify-string.h:623:26: note: in expansion of macro '__fortify_memcpy_chk'
   623 | #define memcpy(p, q, s)  __fortify_memcpy_chk(p, q, s,                  \
       |                          ^~~~~~~~~~~~~~~~~~~~
/kisskb/src/arch/s390/kernel/setup.c:526:9: note: in expansion of macro 'memcpy'
   526 |         memcpy(abs_lc->cregs_save_area, S390_lowcore.cregs_save_area,
       |         ^~~~~~

Looks like this was "'__builtin_memcpy' offset [0, 127] is out of the bounds
[0, 0]" before.

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

  reply	other threads:[~2023-01-16 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 15:29 Linux 6.2-rc4 Linus Torvalds
2023-01-16 12:29 ` Build regressions/improvements in v6.2-rc4 Geert Uytterhoeven
2023-01-16 12:36   ` Geert Uytterhoeven [this message]
2023-01-16 16:40     ` Heiko Carstens
2023-01-16 18:41       ` Guenter Roeck
2023-01-17  8:57         ` Heiko Carstens
2023-01-17  9:03           ` Guenter Roeck
2023-01-16 18:50   ` Guenter Roeck
2023-01-16 18:52 ` Linux 6.2-rc4 Guenter Roeck
2023-01-16 18:57   ` Linus Torvalds

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=46ba7912-3df6-dff9-792-49f4eaadefec@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.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;
as well as URLs for NNTP newsgroup(s).