All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [GIT PULL] meminit fix for v5.2-rc6
Date: Mon, 17 Jun 2019 21:00:28 -0700	[thread overview]
Message-ID: <201906172056.CDD757E@keescook> (raw)

Hi Linus,

Please pull this fix for what I'm calling "meminit" (the compiler-based
variable-init stuff) for v5.2-rc6. This is a small update to the stack
auto-initialization self-test code to deal with the Clang initialization
pattern. It's been in linux-next for a couple weeks; I had waited a bit
wondering if anything more substantial was going to show up, but nothing
has, so I'm sending this now before it gets too late.

Thanks!

-Kees

The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:

  Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/meminit-v5.2-rc6

for you to fetch changes up to 8c30d32b1a326bb120635a8b4836ec61cba454fa:

  lib/test_stackinit: Handle Clang auto-initialization pattern (2019-06-05 07:36:43 -0700)

----------------------------------------------------------------
compiler-based memory initialization update

- Update stack auto-initialization selftest for Clang initialization pattern

----------------------------------------------------------------
Kees Cook (1):
      lib/test_stackinit: Handle Clang auto-initialization pattern

 lib/test_stackinit.c | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2019-06-18  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  4:00 Kees Cook [this message]
2019-06-18 18:05 ` [GIT PULL] meminit fix for v5.2-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=201906172056.CDD757E@keescook \
    --to=keescook@chromium.org \
    --cc=ard.biesheuvel@linaro.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.