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.18-rc2
Date: Sun, 10 Apr 2022 13:37:45 +0200 [thread overview]
Message-ID: <YlLBiR9CNt5SchiE@zn.tnic> (raw)
Hi Linus,
please pull a couple of urgent x86 fixes for 5.18-rc2.
Thx.
---
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -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.18_rc2
for you to fetch changes up to 59b18a1e65b7a2134814106d0860010e10babe18:
x86/msi: Fix msi message data shadow struct (2022-04-07 15:19:32 +0200)
----------------------------------------------------------------
- Fix the MSI message data struct definition
- Use local labels in the exception table macros to avoid symbol
conflicts with clang LTO builds
- A couple of fixes to objtool checking of the relatively newly added
SLS and IBT code
- Rename a local var in the WARN* macro machinery to prevent shadowing
----------------------------------------------------------------
Dave Hansen (1):
x86/mm/tlb: Revert retpoline avoidance approach
Nick Desaulniers (1):
x86/extable: Prefer local labels in .set directives
Peter Zijlstra (3):
objtool: Fix IBT tail-call detection
objtool: Fix SLS validation for kcov tail-call replacement
x86,bpf: Avoid IBT objtool warning
Reto Buerki (1):
x86/msi: Fix msi message data shadow struct
Vincent Mailhol (1):
x86/bug: Prevent shadowing in __WARN_FLAGS
arch/x86/include/asm/asm.h | 20 ++++++++++----------
arch/x86/include/asm/bug.h | 4 ++--
arch/x86/include/asm/msi.h | 19 +++++++++++--------
arch/x86/mm/tlb.c | 37 +++++--------------------------------
arch/x86/net/bpf_jit_comp.c | 1 +
tools/objtool/check.c | 30 +++++++++++++++++++++++++-----
6 files changed, 54 insertions(+), 57 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2022-04-10 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 11:37 Borislav Petkov [this message]
2022-04-10 17:52 ` [GIT PULL] x86/urgent for v5.18-rc2 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=YlLBiR9CNt5SchiE@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.