From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
acme@redhat.com, aik@amd.com, akpm@linux-foundation.org,
alexander.shishkin@linux.intel.com, ardb@kernel.org,
ast@kernel.org, bp@alien8.de, brijesh.singh@amd.com,
changbin.du@huawei.com, christophe.leroy@csgroup.eu,
corbet@lwn.net, daniel.sneddon@linux.intel.com,
dave.hansen@linux.intel.com, ebiggers@google.com,
geert+renesas@glider.be, houtao1@huawei.com, hpa@zytor.com,
jgg@ziepe.ca, jgross@suse.com, jpoimboe@kernel.org,
kai.huang@intel.com, kees@kernel.org, leitao@debian.org,
linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux@rasmusvillemoes.dk, luto@kernel.org, mcgrof@kernel.org,
mhiramat@kernel.org, michael.roth@amd.com, mingo@kernel.org,
mingo@redhat.com, namhyung@kernel.org, paulmck@kernel.org,
pawan.kumar.gupta@linux.intel.com, peterz@infradead.org,
rick.p.edgecombe@intel.com, rppt@kernel.org,
sandipan.das@amd.com, shijie@os.amperecomputing.com,
sohil.mehta@intel.com, tglx@linutronix.de, tj@kernel.org,
tony.luck@intel.com, vegard.nossum@oracle.com, x86@kernel.org,
xin3.li@intel.com, xiongwei.song@windriver.com,
ytcoode@gmail.com
Subject: Re: [PATCHv6 07/16] x86/vsyscall: Reorganize the #PF emulation code
Date: Mon, 23 Jun 2025 08:32:53 -0700 [thread overview]
Message-ID: <bd81a98b-f8d4-4304-ac55-d4151a1a77ab@intel.com> (raw)
In-Reply-To: <kthmv63jrvrr3shhzhhcib7qrjp7sjkah65kogbfphfr6wg6cb@z5zydz6ov7pv>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On 6/23/25 05:41, Kirill A. Shutemov wrote:
> So, IIUC, that's dependency of vsyscall PF on NX. Do we want to disable
> vsyscall on boot if NX is not available?
Well, vsyscall=none can break old userspace, so forcing it on old
hardware doesn't seem like a great idea.
But, either way, this doesn't really appear to be a LASS issue. This code:
> if (!(error_code & X86_PF_INSTR)) {
> /* Failed vsyscall read */
> if (vsyscall_mode == EMULATE)
> return false;
Is really asking the question:
Is this #PF from an instruction fetch in the vsyscall page?
That _should_ be able to be done by comparing CR2 and regs->rip. In
fact, that's done just below anyway:
WARN_ON_ONCE(address != regs->ip);
So I think we can fix this up with something like the attached patch
which just drives the if() from regs->rip and make the warning NX-only.
But this code has been like this a long time and I'm 99% sure the x86
selftests poke at all these cases. I'm curious what they do on those old
P4's (or a 64-bit VM with NX turned off), but it's not super important
either way.
[-- Attachment #2: vsyscall-nx.patch --]
[-- Type: text/x-patch, Size: 1152 bytes --]
diff --git a/arch/x86/entry/vsyscall/vsyscall_64.c b/arch/x86/entry/vsyscall/vsyscall_64.c
index c9103a6fa06e..0b0e0283994f 100644
--- a/arch/x86/entry/vsyscall/vsyscall_64.c
+++ b/arch/x86/entry/vsyscall/vsyscall_64.c
@@ -124,7 +124,8 @@ bool emulate_vsyscall(unsigned long error_code,
if ((error_code & (X86_PF_WRITE | X86_PF_USER)) != X86_PF_USER)
return false;
- if (!(error_code & X86_PF_INSTR)) {
+ /* Avoid emulation unless userspace was executing from vsyscall page: */
+ if (address != regs->ip) {
/* Failed vsyscall read */
if (vsyscall_mode == EMULATE)
return false;
@@ -136,13 +137,16 @@ bool emulate_vsyscall(unsigned long error_code,
return false;
}
+
+ /* X86_PF_INSTR is only set when NX is supported: */
+ if (cpu_feature_enabled(X86_FEATURE_NX))
+ WARN_ON_ONCE(!(error_code & X86_PF_INSTR));
+
/*
* No point in checking CS -- the only way to get here is a user mode
* trap to a high address, which means that we're in 64-bit user code.
*/
- WARN_ON_ONCE(address != regs->ip);
-
if (vsyscall_mode == NONE) {
warn_bad_vsyscall(KERN_INFO, regs,
"vsyscall attempted with vsyscall=none");
next prev parent reply other threads:[~2025-06-23 15:32 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:53 [PATCHv6 00/16] x86: Enable Linear Address Space Separation support Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 01/16] x86/cpu: Enumerate the LASS feature bits Kirill A. Shutemov
2025-06-20 15:25 ` Dave Hansen
2025-06-20 15:36 ` Xin Li
2025-06-20 17:31 ` Kirill A. Shutemov
2025-06-20 23:46 ` Xin Li
2025-06-21 0:45 ` H. Peter Anvin
2025-06-21 0:50 ` H. Peter Anvin
2025-06-23 17:40 ` Xin Li
2025-06-24 2:04 ` H. Peter Anvin
2025-06-24 4:57 ` Xin Li
2025-06-24 5:11 ` Xin Li
2025-06-20 16:02 ` Randy Dunlap
2025-06-20 16:12 ` Xin Li
2025-06-20 16:16 ` Randy Dunlap
2025-06-20 16:35 ` Borislav Petkov
2025-06-20 17:33 ` Kirill A. Shutemov
2025-06-20 18:29 ` Borislav Petkov
2025-06-23 8:17 ` Kirill A. Shutemov
2025-06-23 10:21 ` Borislav Petkov
2025-06-23 13:42 ` Kirill A. Shutemov
2025-06-26 15:18 ` Borislav Petkov
2025-06-26 16:07 ` Borislav Petkov
2025-06-26 17:21 ` Dave Hansen
2025-06-27 10:25 ` Kirill A. Shutemov
2025-06-27 10:43 ` Borislav Petkov
2025-06-27 13:57 ` Dave Hansen
2025-06-20 18:14 ` Sohil Mehta
2025-06-20 18:24 ` Dave Hansen
2025-06-20 23:10 ` Sohil Mehta
2025-06-23 16:25 ` Luck, Tony
2025-06-23 16:42 ` Dave Hansen
2025-06-23 23:13 ` Luck, Tony
2025-06-23 23:36 ` H. Peter Anvin
2025-06-24 0:10 ` Luck, Tony
2025-06-24 2:03 ` H. Peter Anvin
2025-06-25 18:51 ` H. Peter Anvin
2025-06-20 13:53 ` [PATCHv6 02/16] x86/asm: Introduce inline memcpy and memset Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 03/16] x86/alternatives: Disable LASS when patching kernel alternatives Kirill A. Shutemov
2025-06-20 15:33 ` Dave Hansen
2025-06-20 17:18 ` Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 04/16] x86/efi: Move runtime service initialization to arch/x86 Kirill A. Shutemov
2025-06-20 15:35 ` Dave Hansen
2025-06-20 17:42 ` Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 05/16] x86/cpu: Defer CR pinning setup until after EFI initialization Kirill A. Shutemov
2025-06-20 15:44 ` Dave Hansen
2025-06-20 13:53 ` [PATCHv6 06/16] efi: Disable LASS around set_virtual_address_map() EFI call Kirill A. Shutemov
2025-06-20 15:55 ` Dave Hansen
2025-06-20 17:50 ` Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 07/16] x86/vsyscall: Reorganize the #PF emulation code Kirill A. Shutemov
2025-06-20 18:43 ` Dave Hansen
2025-06-20 23:08 ` Andrew Cooper
2025-06-20 23:18 ` Sohil Mehta
2025-06-20 23:29 ` Andrew Cooper
2025-06-20 23:21 ` Dave Hansen
2025-06-21 3:35 ` H. Peter Anvin
2025-06-23 12:41 ` Kirill A. Shutemov
2025-06-23 12:46 ` Andrew Cooper
2025-06-23 15:32 ` Dave Hansen [this message]
2025-06-23 15:45 ` Andrew Cooper
2025-06-24 11:37 ` Kirill A. Shutemov
2025-06-24 14:11 ` Dave Hansen
2025-06-24 14:59 ` [PATCH] x86/vsyscall: Do not require X86_PF_INSTR to emulate vsyscall Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 08/16] x86/traps: Consolidate user fixups in exc_general_protection() Kirill A. Shutemov
2025-06-20 14:47 ` Dave Hansen
2025-06-20 13:53 ` [PATCHv6 09/16] x86/vsyscall: Add vsyscall emulation for #GP Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 10/16] x86/vsyscall: Disable LASS if vsyscall mode is set to EMULATE Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 11/16] x86/cpu: Set LASS CR4 bit as pinning sensitive Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 12/16] x86/traps: Communicate a LASS violation in #GP message Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 13/16] x86/traps: Handle LASS thrown #SS Kirill A. Shutemov
2025-06-20 15:20 ` Xin Li
2025-06-20 17:53 ` Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 14/16] x86/cpu: Make LAM depend on LASS Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 15/16] x86/cpu: Enable LASS during CPU initialization Kirill A. Shutemov
2025-06-20 13:53 ` [PATCHv6 16/16] x86: Re-enable Linear Address Masking Kirill A. Shutemov
2025-06-20 15:38 ` [PATCHv6 00/16] x86: Enable Linear Address Space Separation support Dave Hansen
2025-06-20 22:04 ` Andrew Cooper
2025-06-20 22:29 ` H. Peter Anvin
2025-06-20 22:43 ` H. Peter Anvin
2025-06-20 22:46 ` Dave Hansen
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=bd81a98b-f8d4-4304-ac55-d4151a1a77ab@intel.com \
--to=dave.hansen@intel.com \
--cc=acme@redhat.com \
--cc=aik@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=changbin.du@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=geert+renesas@glider.be \
--cc=houtao1@huawei.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=jgross@suse.com \
--cc=jpoimboe@kernel.org \
--cc=kai.huang@intel.com \
--cc=kees@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luto@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=sandipan.das@amd.com \
--cc=shijie@os.amperecomputing.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=vegard.nossum@oracle.com \
--cc=x86@kernel.org \
--cc=xin3.li@intel.com \
--cc=xiongwei.song@windriver.com \
--cc=ytcoode@gmail.com \
/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).