mirror of https://lore.kernel.org/lkml/
 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/urgent for 6.16-rc3
Date: Mon, 16 Jun 2025 10:55:28 -0700	[thread overview]
Message-ID: <20250616175528.1973014-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Please pull some x86/urgent changes for 6.16-rc3.

This is a pretty scattered set of fixes. The majority of them are further
fixups around the recent ITS mitigations. The rest don't really have a
coherent story.

 * Some flavors of Xen PV guests don't support large pages, but the
   set_memory.c code assumes all CPUs support them. Avoid problems with
   a quick CPU feature check.
 * The TDX code has some wrappers to help retry calls to the TDX module.
   They use function pointers to assembly functions and the compiler
   usually generates direct CALLs. But some new compilers, plus -Os
   turned them in to indirect CALLs and the assembly code was not
   annotated for indirect calls. Force inlining of the helper to fix
   it up.
 * Last, a FRED issue showed up when single-stepping. It's fine when
   using an external debugger, but was getting stuck returning from
   a SIGTRAP handler otherwise. Clear the FRED "swevent" bit to ensure
   that forward progress is made.

--

The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_6.16-rc3

for you to fetch changes up to 7cd9a11dd0c3d1dd225795ed1b5b53132888e7b5:

  Revert "mm/execmem: Unify early execmem_cache behaviour" (2025-06-11 11:20:52 +0200)

----------------------------------------------------------------
 * Further fixups for ITS mitigation
 * Avoid using large pages for kernel mappings when PSE is not enumerated
 * Avoid ever making indirect calls to TDX assembly helpers
 * Fix a FRED single step issue when not using an external debugger

----------------------------------------------------------------
Juergen Gross (1):
      x86/mm/pat: don't collapse pages without PSE set

Kai Huang (1):
      x86/virt/tdx: Avoid indirect calls to TDX assembly functions

Mike Rapoport (Microsoft) (3):
      x86/Kconfig: only enable ROX cache in execmem when STRICT_MODULE_RWX is set
      x86/its: move its_pages array to struct mod_arch_specific
      Revert "mm/execmem: Unify early execmem_cache behaviour"

Peter Zijlstra (Intel) (1):
      x86/its: explicitly manage permissions for ITS pages

Xin Li (Intel) (2):
      x86/fred/signal: Prevent immediate repeat of single step trap on return from SIGTRAP handler
      selftests/x86: Add a test to detect infinite SIGTRAP handler loop

 arch/x86/Kconfig                           |   2 +-
 arch/x86/include/asm/module.h              |   8 +++
 arch/x86/include/asm/sighandling.h         |  22 +++++++
 arch/x86/include/asm/tdx.h                 |   2 +-
 arch/x86/kernel/alternative.c              |  79 +++++++++++++++-------
 arch/x86/kernel/signal_32.c                |   4 ++
 arch/x86/kernel/signal_64.c                |   4 ++
 arch/x86/mm/init_32.c                      |   3 -
 arch/x86/mm/init_64.c                      |   3 -
 arch/x86/mm/pat/set_memory.c               |   3 +
 arch/x86/virt/vmx/tdx/tdx.c                |   5 +-
 include/linux/execmem.h                    |   8 +--
 include/linux/module.h                     |   5 --
 mm/execmem.c                               |  40 +-----------
 tools/testing/selftests/x86/Makefile       |   2 +-
 tools/testing/selftests/x86/sigtrap_loop.c | 101 +++++++++++++++++++++++++++++
 16 files changed, 207 insertions(+), 84 deletions(-)
 create mode 100644 tools/testing/selftests/x86/sigtrap_loop.c

             reply	other threads:[~2025-06-16 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 17:55 Dave Hansen [this message]
2025-06-16 19:00 ` 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=20250616175528.1973014-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

all inboxes | Powered by JetHome®