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/core for 6.1
Date: Tue, 4 Oct 2022 11:57:36 +0200 [thread overview]
Message-ID: <YzwDkPQtUXDQU5km@zn.tnic> (raw)
Hi Linus,
please pull two x86/core fixes for 6.1.
Thx.
---
The following changes since commit b90cb1053190353cc30f0fef0ef1f378ccc063c5:
Linux 6.0-rc3 (2022-08-28 15:05:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_core_for_v6.1_rc1
for you to fetch changes up to 8c03af3e090e9d57d90f482d344563dd4bae1e66:
x86,retpoline: Be sure to emit INT3 after JMP *%\reg (2022-09-15 16:13:53 +0200)
----------------------------------------------------------------
- Make sure an INT3 is slapped after every unconditional retpoline JMP
as both vendors suggest
- Clean up pciserial a bit
----------------------------------------------------------------
Peter Zijlstra (2):
x86/earlyprintk: Clean up pciserial
x86,retpoline: Be sure to emit INT3 after JMP *%\reg
arch/x86/kernel/alternative.c | 9 +++++++++
arch/x86/kernel/early_printk.c | 14 +++++++-------
arch/x86/net/bpf_jit_comp.c | 4 +++-
include/linux/pci_ids.h | 3 +++
4 files changed, 22 insertions(+), 8 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-10-04 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 9:57 Borislav Petkov [this message]
2022-10-04 17:34 ` [GIT PULL] x86/core for 6.1 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=YzwDkPQtUXDQU5km@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;
as well as URLs for NNTP newsgroup(s).