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.16-rc7
Date: Sun, 26 Dec 2021 13:39:46 +0100 [thread overview]
Message-ID: <YchikpZ6h1ViNUDv@zn.tnic> (raw)
Hi Linus,
please pull a couple more x86/urgent fixes for 5.16.
Thx.
---
The following changes since commit 2585cf9dfaaddf00b069673f27bb3f8530e2039c:
Linux 5.16-rc5 (2021-12-12 14:53:01 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.16_rc7
for you to fetch changes up to 57690554abe135fee81d6ac33cc94d75a7e224bb:
x86/pkey: Fix undefined behaviour with PKRU_WD_BIT (2021-12-19 22:44:34 +0100)
----------------------------------------------------------------
- Prevent potential undefined behavior due to shifting pkey constants into the sign bit
- Move the EFI memory reservation code *after* the efi= cmdline parsing has happened
- Revert two commits which turned out to be the wrong direction to chase
when accommodating early memblock reservations consolidation and command line parameters
parsing
----------------------------------------------------------------
Andrew Cooper (1):
x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
Borislav Petkov (2):
Revert "x86/boot: Mark prepare_command_line() __init"
Revert "x86/boot: Pull up cmdline preparation and early param parsing"
Mike Rapoport (1):
x86/boot: Move EFI range reservation after cmdline parsing
arch/x86/include/asm/pkru.h | 4 +--
arch/x86/kernel/setup.c | 72 +++++++++++++++++++--------------------------
2 files changed, 32 insertions(+), 44 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2021-12-26 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 12:39 Borislav Petkov [this message]
2021-12-26 18:38 ` [GIT PULL] x86/urgent for v5.16-rc7 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=YchikpZ6h1ViNUDv@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 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.