linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Joonwon Kang <kjw1627@gmail.com>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] gcc-plugins update for v5.4-rc1
Date: Mon, 16 Sep 2019 14:44:54 -0700	[thread overview]
Message-ID: <201909161443.8AB608118@keescook> (raw)

Hi Linus,

Please pull this tiny gcc-plugins update for v5.4-rc1. It fixes a
potential problem in structure auto-selection (that was not triggered by
any existing kernel structures). This has been in linux-next for about 5
weeks.

Thanks!

-Kees

The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:

  Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v5.4-rc1

for you to fetch changes up to 60f2c82ed20bde57c362e66f796cf9e0e38a6dbb:

  randstruct: Check member structs in is_pure_ops_struct() (2019-07-31 13:13:22 -0700)

----------------------------------------------------------------
randomize_layout: Fix potential auto-selection bug

- Fix auto-selection bug in is_pure_ops_struct (Joonwon Kang)

----------------------------------------------------------------
Joonwon Kang (1):
      randstruct: Check member structs in is_pure_ops_struct()

 scripts/gcc-plugins/randomize_layout_plugin.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2019-09-16 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:44 Kees Cook [this message]
2019-09-21 17:10 ` [GIT PULL] gcc-plugins update for v5.4-rc1 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=201909161443.8AB608118@keescook \
    --to=keescook@chromium.org \
    --cc=kjw1627@gmail.com \
    --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).