From: "Chen, Yian" <yian.chen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ravi Shankar <ravi.v.shankar@intel.com>,
"Tony Luck" <tony.luck@intel.com>,
Paul Lai <paul.c.lai@intel.com>
Subject: Re: [PATCH 3/7] x86/cpu: Disable kernel LASS when patching kernel alternatives
Date: Wed, 11 Jan 2023 16:27:49 -0800 [thread overview]
Message-ID: <ad2da884-c8c8-bc57-e21f-452a08cb10cc@intel.com> (raw)
In-Reply-To: <693d8332-3b86-3dcf-fc87-5c3a08a752db@intel.com>
On 1/10/2023 2:41 PM, Sohil Mehta wrote:
> On 1/9/2023 9:52 PM, Yian Chen wrote:
>
>> LASS stops access to a lower half address in kernel,
>> and this can be deactivated if AC bit in EFLAGS
>> register is set. Hence use stac and clac instructions
>> around access to the address to avoid triggering a
>> LASS #GP fault.
>>
>
> It seems we are implicitly relying on the on stac() and clac() calls
> that are added for SMAP. Have you tried running with SMAP disabled i.e
> "clearcpuid=smap"?
>
Yes, I tested with clearcpuid=smap.
> I believe there needs to be a dependency between LASS and SMAP.
>
Yes, In kernel mode, LASS depends on SMAP to work. And in user mode, it
doesn't, so the dependency description in following may miss user space
effect.
> diff --git a/arch/x86/kernel/cpu/cpuid-deps.c
> b/arch/x86/kernel/cpu/cpuid-deps.c
> index d95221117129..00bc7e4a65d2 100644
> --- a/arch/x86/kernel/cpu/cpuid-deps.c
> +++ b/arch/x86/kernel/cpu/cpuid-deps.c
> @@ -79,6 +79,7 @@ static const struct cpuid_dep cpuid_deps[] = {
> { X86_FEATURE_XFD, X86_FEATURE_XSAVES },
> { X86_FEATURE_XFD, X86_FEATURE_XGETBV1 },
> { X86_FEATURE_AMX_TILE, X86_FEATURE_XFD },
> + { X86_FEATURE_LASS, X86_FEATURE_SMAP },
> {}
> };
Thanks,
Yian
next prev parent reply other threads:[~2023-01-12 0:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 5:51 [PATCH 0/7] Enable LASS (Linear Address space Separation) Yian Chen
2023-01-10 5:51 ` [PATCH 1/7] x86/cpu: Enumerate LASS CPUID and CR4 bits Yian Chen
2023-01-10 20:14 ` Sohil Mehta
2023-01-11 0:13 ` Dave Hansen
2023-01-11 23:23 ` Chen, Yian
2023-01-12 0:06 ` Luck, Tony
2023-01-12 0:15 ` Chen, Yian
2023-01-11 19:21 ` Chen, Yian
2023-01-10 5:51 ` [PATCH 2/7] x86: Add CONFIG option X86_LASS Yian Chen
2023-01-10 21:05 ` Sohil Mehta
2023-01-12 0:13 ` Chen, Yian
2023-01-10 5:52 ` [PATCH 3/7] x86/cpu: Disable kernel LASS when patching kernel alternatives Yian Chen
2023-01-10 21:04 ` Peter Zijlstra
2023-01-11 1:01 ` Chen, Yian
2023-01-11 9:10 ` Peter Zijlstra
2023-01-10 22:41 ` Sohil Mehta
2023-01-12 0:27 ` Chen, Yian [this message]
2023-01-12 0:37 ` Dave Hansen
2023-01-12 18:36 ` Chen, Yian
2023-01-12 18:48 ` Dave Hansen
2023-02-01 2:25 ` Sohil Mehta
2023-02-01 18:20 ` Dave Hansen
2023-02-01 2:10 ` Sohil Mehta
2023-01-10 5:52 ` [PATCH 4/7] x86/vsyscall: Setup vsyscall to compromise LASS protection Yian Chen
2023-01-11 0:34 ` Sohil Mehta
2023-01-12 1:43 ` Chen, Yian
2023-01-12 2:49 ` Sohil Mehta
2023-01-21 4:09 ` Andy Lutomirski
2023-01-10 5:52 ` [PATCH 5/7] x86/cpu: Enable LASS (Linear Address Space Separation) Yian Chen
2023-01-11 22:22 ` Sohil Mehta
2023-01-12 17:56 ` Chen, Yian
2023-01-12 18:17 ` Dave Hansen
2023-01-13 1:17 ` Sohil Mehta
2023-01-13 19:39 ` Sohil Mehta
2023-01-10 5:52 ` [PATCH 6/7] x86/cpu: Set LASS as pinning sensitive CR4 bit Yian Chen
2023-01-10 5:52 ` [PATCH 7/7] x86/kvm: Expose LASS feature to VM guest Yian Chen
2023-02-07 3:21 ` Wang, Lei
2023-02-09 17:18 ` Sean Christopherson
2023-01-10 19:48 ` [PATCH 0/7] Enable LASS (Linear Address space Separation) Sohil Mehta
2023-01-10 22:57 ` 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=ad2da884-c8c8-bc57-e21f-452a08cb10cc@intel.com \
--to=yian.chen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=paul.c.lai@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=sohil.mehta@intel.com \
--cc=tony.luck@intel.com \
--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