From: Borislav Petkov <bp@alien8.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 v6.2-rc2
Date: Sun, 1 Jan 2023 16:07:25 +0100 [thread overview]
Message-ID: <Y7GhrV4YgFGdiHFP@zn.tnic> (raw)
Hi Linus,
pls pull a couple of urgent x86 fixes for 6.2.
Thx.
---
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v6.2_rc2
for you to fetch changes up to 63dc6325ff41ee9e570bde705ac34a39c5dbeb44:
x86/kprobes: Fix optprobe optimization check with CONFIG_RETHUNK (2022-12-27 12:51:58 +0100)
----------------------------------------------------------------
- Two fixes to correct how kprobes handles INT3 now that they're added by other
functionality like the rethunks and not only kgdb
- Remove __init section markings of two functions which are referenced by a
function in the .text section
----------------------------------------------------------------
Arnd Bergmann (1):
x86/calldepth: Fix incorrect init section references
Masami Hiramatsu (Google) (2):
x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK
x86/kprobes: Fix optprobe optimization check with CONFIG_RETHUNK
arch/x86/kernel/callthunks.c | 4 ++--
arch/x86/kernel/kprobes/core.c | 10 +++++++---
arch/x86/kernel/kprobes/opt.c | 28 ++++++++--------------------
3 files changed, 17 insertions(+), 25 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-01-01 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 15:07 Borislav Petkov [this message]
2023-01-01 19:30 ` 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=Y7GhrV4YgFGdiHFP@zn.tnic \
--to=bp@alien8.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
all inboxes | Powered by JetHome®