From: Kees Cook <keescook@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-s390@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
linux-sh@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.0-rc4
Date: Wed, 7 Sep 2022 16:47:33 -0700 [thread overview]
Message-ID: <202209071646.A95761A@keescook> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2209050944290.964530@ramsan.of.borg>
On Mon, Sep 05, 2022 at 09:46:01AM +0200, Geert Uytterhoeven wrote:
> On Mon, 5 Sep 2022, Geert Uytterhoeven wrote:
> > JFYI, when comparing v6.0-rc4[1] to v6.0-rc3[3], the summaries are:
> > - build errors: +3/-16
>
> + /kisskb/src/arch/sh/kernel/machvec.c: error: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Werror=array-bounds]: => 105:33
>
> sh4-gcc11/sh-allyesconfig (-Werror)
Sent a patch for this:
https://lore.kernel.org/linux-hardening/20220907234345.96798-1-keescook@chromium.org/
> + /kisskb/src/include/linux/fortify-string.h: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]: => 258:25
>
> s390x-gcc11/s390-allyesconfig (inlined from 'copy_process' at /kisskb/src/kernel/fork.c:2200:2)
This error appears to have vanished?
> > [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/b90cb1053190353cc30f0fef0ef1f378ccc063c5/ (all 135 configs)
Status Date/time Target
OK Sep 7, 13:54 linus/s390-allyesconfig/s390x-gcc11
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
amd-gfx@lists.freedesktop.org, linux-s390@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.0-rc4
Date: Wed, 7 Sep 2022 16:47:33 -0700 [thread overview]
Message-ID: <202209071646.A95761A@keescook> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2209050944290.964530@ramsan.of.borg>
On Mon, Sep 05, 2022 at 09:46:01AM +0200, Geert Uytterhoeven wrote:
> On Mon, 5 Sep 2022, Geert Uytterhoeven wrote:
> > JFYI, when comparing v6.0-rc4[1] to v6.0-rc3[3], the summaries are:
> > - build errors: +3/-16
>
> + /kisskb/src/arch/sh/kernel/machvec.c: error: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Werror=array-bounds]: => 105:33
>
> sh4-gcc11/sh-allyesconfig (-Werror)
Sent a patch for this:
https://lore.kernel.org/linux-hardening/20220907234345.96798-1-keescook@chromium.org/
> + /kisskb/src/include/linux/fortify-string.h: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]: => 258:25
>
> s390x-gcc11/s390-allyesconfig (inlined from 'copy_process' at /kisskb/src/kernel/fork.c:2200:2)
This error appears to have vanished?
> > [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/b90cb1053190353cc30f0fef0ef1f378ccc063c5/ (all 135 configs)
Status Date/time Target
OK Sep 7, 13:54 linus/s390-allyesconfig/s390x-gcc11
--
Kees Cook
next prev parent reply other threads:[~2022-09-08 2:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 20:22 Linux 6.0-rc4 Linus Torvalds
2022-09-05 7:19 ` Build regressions/improvements in v6.0-rc4 Geert Uytterhoeven
2022-09-05 7:46 ` Geert Uytterhoeven
2022-09-05 7:46 ` Geert Uytterhoeven
2022-09-06 21:42 ` Kees Cook
2022-09-06 21:42 ` Kees Cook
2022-09-07 23:47 ` Kees Cook [this message]
2022-09-07 23:47 ` Kees Cook
2022-09-05 12:56 ` Linux 6.0-rc4 Guenter Roeck
2022-09-10 17:44 ` Linus Torvalds
2022-09-10 18:13 ` Guenter Roeck
2022-09-10 21:32 ` Linus Torvalds
2022-09-12 7:00 ` Csókás Bence
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=202209071646.A95761A@keescook \
--to=keescook@chromium.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.