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/fsgsbase updates for v5.10
Date: Mon, 12 Oct 2020 12:43:27 +0200 [thread overview]
Message-ID: <20201012104327.GG25311@zn.tnic> (raw)
Hi Linus,
please pull some small x86/fsgsbase updates.
Thx.
---
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_fsgsbase_for_v5.10
for you to fetch changes up to 1b9abd1755ad947d7c9913e92e7837b533124c90:
selftests/x86/fsgsbase: Test PTRACE_PEEKUSER for GSBASE with invalid LDT GS (2020-08-26 20:54:18 +0200)
----------------------------------------------------------------
* Misc minor cleanups and corrections to the fsgsbase code and
respective selftests.
----------------------------------------------------------------
Andy Lutomirski (2):
selftests/x86/fsgsbase: Reap a forgotten child
selftests/x86/fsgsbase: Test PTRACE_PEEKUSER for GSBASE with invalid LDT GS
Borislav Petkov (2):
x86/entry/64: Correct the comment over SAVE_AND_SET_GSBASE
x86/fsgsbase: Replace static_cpu_has() with boot_cpu_has()
arch/x86/entry/entry_64.S | 5 ++-
arch/x86/include/asm/fsgsbase.h | 4 +-
arch/x86/kernel/process_64.c | 8 ++--
tools/testing/selftests/x86/fsgsbase.c | 68 ++++++++++++++++++++++++++++++++++
4 files changed, 77 insertions(+), 8 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-10-12 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 10:43 Borislav Petkov [this message]
2020-10-12 18:21 ` [GIT PULL] x86/fsgsbase updates for v5.10 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=20201012104327.GG25311@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).