All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/sgx for 6.16-rc1
Date: Thu, 29 May 2025 11:03:52 -0700	[thread overview]
Message-ID: <20250529180352.1935517-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Continuing the trend of a slow dribble of SGX updates, please pull a
couple x86/sgx changes for 6.16-rc1.

The first one is a no-brainer to use the (simple) SHA-256 library.

For the second one, some folks doing testing noticed that SGX systems
under memory pressure were inducing fatal machine checks at pretty
unnerving rates, despite the SGX code having _some_ awareness of
memory poison. Turns out that the SGX reclaim path was not checking
for poison _and_ it always accesses memory to copy it around. Make
sure that poisoned pages are not reclaimed.

--

The following changes since commit b4432656b36e5cc1d50a1f2dc15357543add530e:

  Linux 6.15-rc4 (2025-04-27 15:19:23 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_sgx_for_6.16-rc1

for you to fetch changes up to ed16618c380c32c68c06186d0ccbb0d5e0586e59:

  x86/sgx: Prevent attempts to reclaim poisoned pages (2025-05-15 19:01:45 +0200)

----------------------------------------------------------------
 * Make SGX less likely to induce fatal machine checks
 * Use much more compact SHA-256 library API

----------------------------------------------------------------
Andrew Zaborowski (1):
      x86/sgx: Prevent attempts to reclaim poisoned pages

Eric Biggers (1):
      x86/sgx: Use SHA-256 library API instead of crypto_shash API

 arch/x86/Kconfig                 |  3 +--
 arch/x86/kernel/cpu/sgx/driver.h |  1 -
 arch/x86/kernel/cpu/sgx/ioctl.c  | 30 ++----------------------------
 arch/x86/kernel/cpu/sgx/main.c   |  2 ++
 4 files changed, 5 insertions(+), 31 deletions(-)

             reply	other threads:[~2025-05-29 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 18:03 Dave Hansen [this message]
2025-05-30  5:25 ` [GIT PULL] x86/sgx for 6.16-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=20250529180352.1935517-1-dave.hansen@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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 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.