public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for v5.19-rc6
Date: Sun, 10 Jul 2022 12:19:00 +0200	[thread overview]
Message-ID: <YsqnlPzrnQThDLil@zn.tnic> (raw)

Hi Linus,

please pull a couple of urgent x86 fixes for 5.19.

Thx.

---

The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:

  Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.19_rc6

for you to fetch changes up to cb8a4beac39b90cd60abbf9fd639a3357274e469:

  x86/boot: Fix the setup data types max limit (2022-07-10 11:17:40 +0200)

----------------------------------------------------------------
- Prepare for and clear .brk early in order to address XenPV guests
failures where the hypervisor verifies page tables and uninitialized
data in that range leads to bogus failures in those checks

- Add any potential setup_data entries supplied at boot to the identity
pagetable mappings to prevent kexec kernel boot failures. Usually, this
is not a problem for the normal kernel as those mappings are part of
the initially mapped 2M pages but if kexec gets to allocate the second
kernel somewhere else, those setup_data entries need to be mapped there
too.

- Fix objtool not to discard text references from the __tracepoints
section so that ENDBR validation still works

- Correct the setup_data types limit as it is user-visible, before 5.19
releases

----------------------------------------------------------------
Borislav Petkov (1):
      x86/boot: Fix the setup data types max limit

Juergen Gross (3):
      x86/xen: Use clear_bss() for Xen PV guests
      x86: Clear .brk area at early boot
      x86: Fix .brk attribute in linker script

Michael Roth (1):
      x86/compressed/64: Add identity mappings for setup_data entries

Peter Zijlstra (1):
      x86/ibt, objtool: Don't discard text references from tracepoint section

 arch/x86/boot/compressed/ident_map_64.c | 13 +++++++++++++
 arch/x86/include/asm/setup.h            |  3 +++
 arch/x86/include/uapi/asm/bootparam.h   |  2 +-
 arch/x86/kernel/head64.c                |  4 +++-
 arch/x86/kernel/vmlinux.lds.S           |  2 +-
 arch/x86/xen/enlighten_pv.c             |  8 ++++++--
 arch/x86/xen/xen-head.S                 | 10 +---------
 tools/objtool/check.c                   |  3 +--
 8 files changed, 29 insertions(+), 16 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

             reply	other threads:[~2022-07-10 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 10:19 Borislav Petkov [this message]
2022-07-10 16:45 ` [GIT PULL] x86/urgent for v5.19-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=YsqnlPzrnQThDLil@zn.tnic \
    --to=bp@suse.de \
    --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