public inbox for linux-kernel@vger.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.12-rc1
Date: Wed, 11 Sep 2024 15:02:28 -0700	[thread overview]
Message-ID: <20240911220228.4051834-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Please pull some x86/sgx changes for 6.12-rc1. These fix a deadlock
in the SGX NUMA allocator. It's probably only triggerable today on
servers with buggy BIOSes, but it's theoretically possible it can
happen on less goofy systems.

--

The following changes since commit 431c1646e1f86b949fa3685efc50b660a364c2b6:

  Linux 6.11-rc6 (2024-09-01 19:46:02 +1200)

are available in the Git repository at:

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

for you to fetch changes up to c8ddc99eeba5f00b65efeae920eec3990bfc34ca:

  x86/sgx: Log information when a node lacks an EPC section (2024-09-05 15:20:47 -0700)

----------------------------------------------------------------
Fix deadlock in SGX NUMA node search

----------------------------------------------------------------
Aaron Lu (2):
      x86/sgx: Fix deadlock in SGX NUMA node search
      x86/sgx: Log information when a node lacks an EPC section

 arch/x86/kernel/cpu/sgx/main.c | 34 +++++++++++++++++++++-------------
 1 file changed, 21 insertions(+), 13 deletions(-)

             reply	other threads:[~2024-09-11 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 22:02 Dave Hansen [this message]
2024-09-16  4:55 ` [GIT PULL] x86/sgx for 6.12-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=20240911220228.4051834-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox