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.16-rc4
Date: Sun, 29 Jun 2025 10:46:30 +0200 [thread overview]
Message-ID: <20250629084630.GAaGD9ZoXfbOG272mA@fat_crate.local> (raw)
Hi Linus,
please pull the x86/urgent lineup for v6.16-rc4.
Thx.
---
The following changes since commit 2aebf5ee43bf0ed225a09a30cf515d9f2813b759:
x86/alternatives: Fix int3 handling failure from broken text_poke array (2025-06-18 13:59:56 +0200)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_urgent_for_v6.16_rc4
for you to fetch changes up to fa7d0f83c5c4223a01598876352473cb3d3bd4d7:
x86/traps: Initialize DR7 by writing its architectural reset value (2025-06-24 13:15:52 -0700)
----------------------------------------------------------------
- Make sure DR6 and DR7 are initialized to their architectural values and not
accidentally cleared, leading to misconfigurations
----------------------------------------------------------------
Xin Li (Intel) (2):
x86/traps: Initialize DR6 by writing its architectural reset value
x86/traps: Initialize DR7 by writing its architectural reset value
arch/x86/include/asm/debugreg.h | 19 +++++++++++++++----
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/include/uapi/asm/debugreg.h | 21 ++++++++++++++++++++-
arch/x86/kernel/cpu/common.c | 24 ++++++++++--------------
arch/x86/kernel/kgdb.c | 2 +-
arch/x86/kernel/process_32.c | 2 +-
arch/x86/kernel/process_64.c | 2 +-
arch/x86/kernel/traps.c | 34 +++++++++++++++++++++-------------
arch/x86/kvm/x86.c | 4 ++--
9 files changed, 72 insertions(+), 38 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2025-06-29 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 8:46 Borislav Petkov [this message]
2025-06-29 16:40 ` 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=20250629084630.GAaGD9ZoXfbOG272mA@fat_crate.local \
--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®