lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27fe1dedb151a606ae46ae3c2bccd80b9a64ff07.camel@intel.com>
Date: Tue, 7 Oct 2025 16:23:45 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Mehta, Sohil" <sohil.mehta@...el.com>, "tglx@...utronix.de"
	<tglx@...utronix.de>, "mingo@...hat.com" <mingo@...hat.com>, "bp@...en8.de"
	<bp@...en8.de>, "x86@...nel.org" <x86@...nel.org>,
	"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
CC: "corbet@....net" <corbet@....net>, "ardb@...nel.org" <ardb@...nel.org>,
	"david.laight.linux@...il.com" <david.laight.linux@...il.com>,
	"luto@...nel.org" <luto@...nel.org>, "jpoimboe@...nel.org"
	<jpoimboe@...nel.org>, "andrew.cooper3@...rix.com"
	<andrew.cooper3@...rix.com>, "Luck, Tony" <tony.luck@...el.com>,
	"alexander.shishkin@...ux.intel.com" <alexander.shishkin@...ux.intel.com>,
	"kas@...nel.org" <kas@...nel.org>, "seanjc@...gle.com" <seanjc@...gle.com>,
	"rdunlap@...radead.org" <rdunlap@...radead.org>, "dwmw@...zon.co.uk"
	<dwmw@...zon.co.uk>, "vegard.nossum@...cle.com" <vegard.nossum@...cle.com>,
	"xin@...or.com" <xin@...or.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-doc@...r.kernel.org"
	<linux-doc@...r.kernel.org>, "kees@...nel.org" <kees@...nel.org>,
	"hpa@...or.com" <hpa@...or.com>, "peterz@...radead.org"
	<peterz@...radead.org>, "linux-efi@...r.kernel.org"
	<linux-efi@...r.kernel.org>, "geert@...ux-m68k.org" <geert@...ux-m68k.org>
Subject: Re: [PATCH v10 00/15] x86: Enable Linear Address Space Separation
 support

On Mon, 2025-10-06 at 23:51 -0700, Sohil Mehta wrote:
> > Userspace accesses
> > ------------------
> > Userspace attempts to access any kernel address generate a #GP when LASS
> > is enabled. Unfortunately, legacy vsyscall functions are located in the
> > address range 0xffffffffff600000 - 0xffffffffff601000. Prior to LASS,
> > default access (XONLY) to the vsyscall page would generate a page fault
> > and the access would be emulated in the kernel. To avoid breaking user
> > applications when LASS is enabled, the patches extend vsyscall emulation
> > in XONLY mode to the #GP handler.
> > 
> > In contrast, the vsyscall EMULATE mode is deprecated and not expected to
> > be used by anyone. Supporting EMULATE mode with LASS would require
> > complex instruction decoding in the #GP fault handler, which is probably
> > not worth the effort. For now, LASS is disabled in the rare case when
> > someone absolutely needs to enable vsyscall=emulate via the command
> > line.

There is also an expected harmless UABI change around SIG_SEGV. For a user mode
kernel address range access, the kernel can deliver a signal that provides the
exception type and the address. Before it was #PF, now a #GP with no address.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ