public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Mike Galbraith <efault@gmx.de>
Subject: [GIT PULL] x86-refcount fix for v4.14-rc3
Date: Wed, 27 Sep 2017 03:29:46 -0700	[thread overview]
Message-ID: <20170927102946.GA54244@beast> (raw)

Hi,

Please pull this x86-refcount fix for v4.14-rc3. This restores the x86
fast-refcount protection after fixing a corner case that was found late
before the merge window opened. This was the only problem seen during
the protection's life in linux-next, so getting this into v4.14 is
highly desired.

Thanks!

-Kees

The following changes since commit e19b205be43d11bff638cad4487008c48d21c103:

  Linux 4.14-rc2 (2017-09-24 16:38:56 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/x86-refcount-v4.14-rc3

for you to fetch changes up to 635fee8f6b725a99f511b8e0eca82c3214b9c678:

  locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT (2017-09-27 03:05:13 -0700)

----------------------------------------------------------------
Fix x86 fast-refcount protection to avoid corner-case of being used a
function living in the .text.unlikely section.

----------------------------------------------------------------
Kees Cook (2):
      locking/refcounts, x86/asm: Use unique .text section for refcount exceptions
      locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT

 arch/x86/Kconfig                  | 2 +-
 arch/x86/include/asm/refcount.h   | 2 +-
 arch/x86/mm/extable.c             | 7 ++++++-
 include/asm-generic/vmlinux.lds.h | 1 +
 4 files changed, 9 insertions(+), 3 deletions(-)

-- 
Kees Cook
Pixel Security

             reply	other threads:[~2017-09-27 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 10:29 Kees Cook [this message]
2017-09-27 10:57 ` [GIT PULL] x86-refcount fix for v4.14-rc3 Ingo Molnar
2017-09-27 11:47   ` Kees Cook
2017-09-27 12:02     ` Ingo Molnar

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=20170927102946.GA54244@beast \
    --to=keescook@chromium.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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