From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexander Popov <alex.popov@linux.com>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [GIT PULL] gcc-plugin updates for v4.20-rc6
Date: Fri, 7 Dec 2018 09:08:45 -0800 [thread overview]
Message-ID: <20181207170845.GA24251@beast> (raw)
Hi Linus,
Please pull these gcc-plugin fixes for v4.20-rc6.
Thanks!
-Kees
The following changes since commit ef1a8409348966f0b25ff97a170d6d0367710ea9:
stackleak: Disable function tracing and kprobes for stackleak_erase() (2018-11-30 09:05:07 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v4.20-rc6
for you to fetch changes up to 8fb2dfb228df785bbeb4d055a74402ef4b07fc25:
stackleak: Register the 'stackleak_cleanup' pass before the '*free_cfg' pass (2018-12-06 09:10:23 -0800)
----------------------------------------------------------------
Fixes for stackleak
- Remove tracing for inserted stack depth marking function (Anders Roxell)
- Move gcc-plugin pass location to avoid objtool warnings (Alexander Popov)
----------------------------------------------------------------
Alexander Popov (1):
stackleak: Register the 'stackleak_cleanup' pass before the '*free_cfg' pass
Anders Roxell (1):
stackleak: Mark stackleak_track_stack() as notrace
kernel/stackleak.c | 2 +-
scripts/gcc-plugins/stackleak_plugin.c | 8 +++++---
2 files changed, 6 insertions(+), 4 deletions(-)
--
Kees Cook
next reply other threads:[~2018-12-07 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 17:08 Kees Cook [this message]
2018-12-07 22:40 ` [GIT PULL] gcc-plugin updates for v4.20-rc6 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=20181207170845.GA24251@beast \
--to=keescook@chromium.org \
--cc=alex.popov@linux.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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).