From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: [GIT PULL] meminit fix for v5.3-rc2
Date: Sun, 28 Jul 2019 12:21:34 -0700 [thread overview]
Message-ID: <201907281218.F6D2C2DD@keescook> (raw)
Hi Linus,
Please pull this meminit fix for v5.3-rc2. This is late in the -rc2
window because I got confused about whether I or akpm was taking this
patch. I noticed it still wasn't in -mm, so here it is. It's a small
Kconfig change that fixes a bunch of build warnings under KASAN and the
gcc-plugin-based stack auto-initialization features (which are arguably
redundant, so better to let KASAN control this).
Thanks!
-Kees
The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:
Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/meminit-v5.3-rc2
for you to fetch changes up to 173e6ee21e2b3f477f07548a79c43b8d9cfbb37d:
structleak: disable STRUCTLEAK_BYREF in combination with KASAN_STACK (2019-07-25 16:16:12 -0700)
----------------------------------------------------------------
meminit fix
- Disable gcc-based stack variable auto-init under KASAN (Arnd Bergmann)
----------------------------------------------------------------
Arnd Bergmann (1):
structleak: disable STRUCTLEAK_BYREF in combination with KASAN_STACK
security/Kconfig.hardening | 7 +++++++
1 file changed, 7 insertions(+)
--
Kees Cook
next reply other threads:[~2019-07-28 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 19:21 Kees Cook [this message]
2019-07-28 19:43 ` [GIT PULL] meminit fix for v5.3-rc2 Linus Torvalds
2019-07-28 19:50 ` Linus Torvalds
2019-07-28 22:16 ` Kees Cook
2019-07-30 13:53 ` Alexander Potapenko
2019-07-30 19:53 ` Linus Torvalds
2019-07-31 11:30 ` Alexander Potapenko
2019-07-28 19:50 ` pr-tracker-bot
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=201907281218.F6D2C2DD@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--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 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).