All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [GIT PULL] Enable -Wstringop-overflow globally
Date: Mon, 22 Jan 2024 09:29:05 -0600	[thread overview]
Message-ID: <Za6JwRpknVIlfhPF@work> (raw)

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/Wstringop-overflow-for-6.8-rc2

for you to fetch changes up to a5e0ace04fbf56c1794b1a2fa7a93672753b3fc7:

  init: Kconfig: Disable -Wstringop-overflow for GCC-11 (2024-01-21 17:45:31 -0600)

----------------------------------------------------------------
Enable -Wstringop-overflow globally

Hi Linus,

Please, pull the following patches that enable -Wstringop-overflow,
globally. These patches have been baking in linux-next for a whole
development cycle.

I waited for the release of -rc1 to run a final build-test on top of
it before sending this pull request. Fortunatelly, after building
358 kernels overnight (basically all supported archs with a wide
variety of configs), no more warnings have surfaced! :)

Thus, we are in a good position to enable this compiler option for
all versions of GCC that support it, with the exception of GCC-11,
which appears to have some issues with this option[1].

[1] https://lore.kernel.org/lkml/b3c99290-40bc-426f-b3d2-1aa903f95c4e@embeddedor.com/

Thanks
--
Gustavo

----------------------------------------------------------------
Gustavo A. R. Silva (2):
      Makefile: Enable -Wstringop-overflow globally
      init: Kconfig: Disable -Wstringop-overflow for GCC-11

 Makefile                   |  4 ++++
 init/Kconfig               | 12 ++++++++++++
 scripts/Makefile.extrawarn |  2 --
 3 files changed, 16 insertions(+), 2 deletions(-)

             reply	other threads:[~2024-01-22 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 15:29 Gustavo A. R. Silva [this message]
2024-01-22 18:02 ` [GIT PULL] Enable -Wstringop-overflow globally pr-tracker-bot
2024-01-26 21:22 ` Linus Torvalds
2024-01-26 21:30   ` Gustavo A. R. Silva
2024-01-26 22:24     ` Kees Cook
2024-01-26 22:36       ` Linus Torvalds
2024-01-27 15:11         ` David Laight
2024-01-27 19:53           ` Gustavo A. R. Silva
2024-01-27 19:53             ` Gustavo A. R. Silva
2024-01-30 14:52             ` Thomas Hellström
2024-01-30 14:52               ` Thomas Hellström
2024-02-02  7:52   ` Arnd Bergmann
2024-02-02 18:29     ` 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=Za6JwRpknVIlfhPF@work \
    --to=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.