linux-hardening.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Daniel Vetter <daniel@ffwll.ch>,
	Dan Williams <dan.j.williams@intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Keith Packard <keithp@keithp.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-hardening@vger.kernel.org
Subject: Re: [GIT PULL] overflow updates for v5.15-rc1
Date: Mon, 6 Sep 2021 12:43:50 +0100	[thread overview]
Message-ID: <20210906114350.GB4309@sirena.org.uk> (raw)
In-Reply-To: <202109051123.11E4E31@keescook>

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

On Sun, Sep 05, 2021 at 11:31:44AM -0700, Kees Cook wrote:
> On Sun, Sep 05, 2021 at 10:36:22AM -0700, Linus Torvalds wrote:

> > > Yeech. Yeah, no, that was not expected at all. I even did test merge builds against your latest tree before sending the Pull Request. This has been in -next for weeks, too.

> > Sadly, I don't think linux-next checks for warnings.

> Oh, I thought I'd gotten such reports from sfr before, but certainly the
> 0day bot and others have yelled loudly about new warnings (from earlier
> iterations of this series in -next).

Yes, Stephen will report new warnings in the configs he tested and
there's a bunch of people who like to go around fixing warnings whenever
they do appear though only in the more common configurations.

> > > What was the build environment?

> > This is actually just bog-standard gcc-11.2 from F34, and an allmodconfig build.

> Ah, fun. Yeah, I'm behind on versions, it seems. Default gcc version on
> latest stable Ubuntu release is 10.3. I will go retest on the devel
> release.

If you're looking for coverage on this stuff it's also good to check
with clang as well, it's sufficiently different that it often triggers
extra stuff (eg, turning on -Werror broke i386 allmodconfig for clang-10
since that triggers some stack frame size warnings which are now
errors).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-09-06 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  3:22 [GIT PULL] overflow updates for v5.15-rc1 Kees Cook
2021-09-04 20:47 ` Linus Torvalds
     [not found]   ` <45312958-B844-4B4C-9808-8205866675A1@chromium.org>
2021-09-05 17:36     ` Linus Torvalds
2021-09-05 18:21       ` Linus Torvalds
2021-09-05 18:31       ` Kees Cook
2021-09-06 11:43         ` Mark Brown [this message]
2021-09-06 17:19           ` Kees Cook
2021-09-05 20:52       ` Kees Cook
2021-09-06  5:27       ` Stephen Rothwell
2021-09-06 17:12         ` Kees Cook

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=20210906114350.GB4309@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=keithp@keithp.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=torvalds@linux-foundation.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).