From: John Allen <john.allen@amd.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"nathan@kernel.org" <nathan@kernel.org>
Cc: "bsingharora@gmail.com" <bsingharora@gmail.com>,
"Syromiatnikov, Eugene" <esyr@redhat.com>,
"babu.moger@amd.com" <babu.moger@amd.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"Eranian, Stephane" <eranian@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"fweimer@redhat.com" <fweimer@redhat.com>,
"nadav.amit@gmail.com" <nadav.amit@gmail.com>,
"jannh@google.com" <jannh@google.com>,
"dethoma@microsoft.com" <dethoma@microsoft.com>,
"kcc@google.com" <kcc@google.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"oleg@redhat.com" <oleg@redhat.com>,
"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"Lutomirski, Andy" <luto@kernel.org>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"jamorris@linux.microsoft.com" <jamorris@linux.microsoft.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"Moreira, Joao" <joao.moreira@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"gustavoars@kernel.org" <gustavoars@kernel.org>,
"rppt@kernel.org" <rppt@kernel.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yang, Weijiang" <weijiang.yang@intel.com>,
"gorcunov@gmail.com" <gorcunov@gmail.com>
Subject: Re: [PATCH v2 33/39] x86/cpufeatures: Limit shadow stack to Intel CPUs
Date: Thu, 3 Nov 2022 12:39:30 -0500 [thread overview]
Message-ID: <67da8e11-c9b1-3445-bf7d-3854cea72b7e@amd.com> (raw)
In-Reply-To: <8429968c22a9532a6855a8fd9e4dd0a7f2344408.camel@intel.com>
On 10/4/22 6:24 PM, Edgecombe, Rick P wrote:
> On Tue, 2022-10-04 at 14:17 -0700, H. Peter Anvin wrote:
>> On October 4, 2022 1:50:20 PM PDT, Nathan Chancellor <
>> nathan@kernel.org> wrote:
>>> On Tue, Oct 04, 2022 at 08:34:54PM +0000, Edgecombe, Rick P wrote:
>>>> On Tue, 2022-10-04 at 14:43 -0500, John Allen wrote:
>>>>> On 10/4/22 10:47 AM, Nathan Chancellor wrote:
>>>>>> Hi Kees,
>>>>>>
>>>>>> On Mon, Oct 03, 2022 at 09:54:26PM -0700, Kees Cook wrote:
>>>>>>> On Mon, Oct 03, 2022 at 05:09:04PM -0700, Dave Hansen
>>>>>>> wrote:
>>>>>>>> On 10/3/22 16:57, Kees Cook wrote:
>>>>>>>>> On Thu, Sep 29, 2022 at 03:29:30PM -0700, Rick
>>>>>>>>> Edgecombe
>>>>>>>>> wrote:
>>>>>>>>>> Shadow stack is supported on newer AMD processors,
>>>>>>>>>> but the
>>>>>>>>>> kernel
>>>>>>>>>> implementation has not been tested on them. Prevent
>>>>>>>>>> basic
>>>>>>>>>> issues from
>>>>>>>>>> showing up for normal users by disabling shadow stack
>>>>>>>>>> on
>>>>>>>>>> all CPUs except
>>>>>>>>>> Intel until it has been tested. At which point the
>>>>>>>>>> limitation should be
>>>>>>>>>> removed.
>>>>>>>>>>
>>>>>>>>>> Signed-off-by: Rick Edgecombe <
>>>>>>>>>> rick.p.edgecombe@intel.com>
>>>>>>>>>
>>>>>>>>> So running the selftests on an AMD system is sufficient
>>>>>>>>> to
>>>>>>>>> drop this
>>>>>>>>> patch?
>>>>>>>>
>>>>>>>> Yes, that's enough.
>>>>>>>>
>>>>>>>> I _thought_ the AMD folks provided some tested-by's at
>>>>>>>> some
>>>>>>>> point in the
>>>>>>>> past. But, maybe I'm confusing this for one of the other
>>>>>>>> shared
>>>>>>>> features. Either way, I'm sure no tested-by's were
>>>>>>>> dropped on
>>>>>>>> purpose.
>>>>>>>>
>>>>>>>> I'm sure Rick is eager to trim down his series and this
>>>>>>>> would
>>>>>>>> be a great
>>>>>>>> patch to drop. Does anyone want to make that easy for
>>>>>>>> Rick?
>>>>>>>>
>>>>>>>> <hint> <hint>
>>>>>>>
>>>>>>> Hey Gustavo, Nathan, or Nick! I know y'all have some fancy
>>>>>>> AMD
>>>>>>> testing
>>>>>>> rigs. Got a moment to spin up this series and run the
>>>>>>> selftests?
>>>>>>> :)
>>>>>>
>>>>>> I do have access to a system with an EPYC 7513, which does
>>>>>> have
>>>>>> Shadow
>>>>>> Stack support (I can see 'shstk' in the "Flags" section of
>>>>>> lscpu
>>>>>> with
>>>>>> this series). As far as I understand it, AMD only added
>>>>>> Shadow
>>>>>> Stack
>>>>>> with Zen 3; my regular AMD test system is Zen 2 (probably
>>>>>> should
>>>>>> look at
>>>>>> procurring a Zen 3 or Zen 4 one at some point).
>>>>>>
>>>>>> I applied this series on top of 6.0 and reverted this change
>>>>>> then
>>>>>> booted
>>>>>> it on that system. After building the selftest (which did
>>>>>> require
>>>>>> 'make headers_install' and a small addition to make it build
>>>>>> beyond
>>>>>> that, see below), I ran it and this was the result. I am not
>>>>>> sure
>>>>>> if
>>>>>> that is expected or not but the other results seem promising
>>>>>> for
>>>>>> dropping this patch.
>>>>>>
>>>>>> $ ./test_shadow_stack_64
>>>>>> [INFO] new_ssp = 7f8a36c9fff8, *new_ssp = 7f8a36ca0001
>>>>>> [INFO] changing ssp from 7f8a374a0ff0 to 7f8a36c9fff8
>>>>>> [INFO] ssp is now 7f8a36ca0000
>>>>>> [OK] Shadow stack pivot
>>>>>> [OK] Shadow stack faults
>>>>>> [INFO] Corrupting shadow stack
>>>>>> [INFO] Generated shadow stack violation successfully
>>>>>> [OK] Shadow stack violation test
>>>>>> [INFO] Gup read -> shstk access success
>>>>>> [INFO] Gup write -> shstk access success
>>>>>> [INFO] Violation from normal write
>>>>>> [INFO] Gup read -> write access success
>>>>>> [INFO] Violation from normal write
>>>>>> [INFO] Gup write -> write access success
>>>>>> [INFO] Cow gup write -> write access success
>>>>>> [OK] Shadow gup test
>>>>>> [INFO] Violation from shstk access
>>>>>> [OK] mprotect() test
>>>>>> [OK] Userfaultfd test
>>>>>> [FAIL] Alt shadow stack test
>>>>>
>>>>> The selftest is looking OK on my system (Dell PowerEdge R6515
>>>>> w/ EPYC
>>>>> 7713). I also just pulled a fresh 6.0 kernel and applied the
>>>>> series
>>>>> including the fix Nathan mentions below.
>>>>>
>>>>> $ tools/testing/selftests/x86/test_shadow_stack_64
>>>>> [INFO] new_ssp = 7f30cccc5ff8, *new_ssp = 7f30cccc6001
>>>>> [INFO] changing ssp from 7f30cd4c6ff0 to 7f30cccc5ff8
>>>>> [INFO] ssp is now 7f30cccc6000
>>>>> [OK] Shadow stack pivot
>>>>> [OK] Shadow stack faults
>>>>> [INFO] Corrupting shadow stack
>>>>> [INFO] Generated shadow stack violation successfully
>>>>> [OK] Shadow stack violation test
>>>>> [INFO] Gup read -> shstk access success
>>>>> [INFO] Gup write -> shstk access success
>>>>> [INFO] Violation from normal write
>>>>> [INFO] Gup read -> write access success
>>>>> [INFO] Violation from normal write
>>>>> [INFO] Gup write -> write access success
>>>>> [INFO] Cow gup write -> write access success
>>>>> [OK] Shadow gup test
>>>>> [INFO] Violation from shstk access
>>>>> [OK] mprotect() test
>>>>> [OK] Userfaultfd test
>>>>> [OK] Alt shadow stack test.
>>>>
>>>> Thanks for the testing. Based on the test, I wonder if this could
>>>> be a
>>>> SW bug. Nathan, could I send you a tweaked test with some more
>>>> debug
>>>> information?
>>>
>>> Yes, more than happy to help you look into this further!
>>>
>>>> John, are we sure AMD and Intel systems behave the same with
>>>> respect to
>>>> CPUs not creating Dirty=1,Write=0 PTEs in rare situations? Or any
>>>> other
>>>> CET related differences we should hash out? Otherwise I'll drop
>>>> the
>>>> patch for the next version. (and assuming the issue Nathan hit
>>>> doesn't
>>>> turn up anything HW related).
>>
>> I have to admit to being a bit confused here... in general, we trust
>> CPUID bits unless they are *known* to be wrong, in which case we
>> blacklist them.
>>
>> If AMD advertises the feature but it doesn't work or they didn't
>> validate it, that would be a (serious!) bug on their part that we can
>> address by blacklisting, but they should also fix with a
>> microcode/BIOS patch.
>>
>> What am I missing?
>
> I have not read anything about the AMD implementation except hearing
> that it is supported. But there are some microarchitectual-like aspects
> to this CET Linux implementation, around requiring CPUs to not create
> Dirty=1,Write=0 PTEs in some cases, where they did in the past. In
> another thread Jann asked how the IOMMU works with respect to this edge
> case and I'm currently trying to chase down that answer for even Intel
> HW. So I just wanted to double check that we expect that everything
> should be the same. In either case we still have time to iron things
> out before anything gets upstream.
Hi Rick,
Sorry for the delayed reply. After asking around, I think you can safely
assume that AMD will not create Dirty=1,Write=0 PTEs in rare
circumstances and shadow stack should behave the same as Intel in that
regard.
Thanks,
John
next prev parent reply other threads:[~2022-11-03 17:39 UTC|newest]
Thread overview: 241+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 22:28 [PATCH v2 00/39] Shadowstacks for userspace Rick Edgecombe
2022-09-29 22:28 ` [PATCH v2 01/39] Documentation/x86: Add CET description Rick Edgecombe
2022-09-30 3:41 ` Bagas Sanjaya
2022-09-30 13:33 ` Jonathan Corbet
2022-09-30 13:41 ` Bagas Sanjaya
2022-10-03 16:56 ` Edgecombe, Rick P
2022-10-04 2:16 ` Bagas Sanjaya
2022-10-05 9:10 ` Peter Zijlstra
2022-10-05 9:25 ` Bagas Sanjaya
2022-10-05 9:46 ` Peter Zijlstra
2022-10-03 19:35 ` John Hubbard
2022-10-03 19:39 ` Dave Hansen
2022-10-04 2:13 ` Bagas Sanjaya
2022-10-03 17:18 ` Kees Cook
2022-10-03 19:46 ` Edgecombe, Rick P
2022-10-05 0:02 ` Andrew Cooper
2022-10-10 12:19 ` Florian Weimer
2022-10-10 16:44 ` Edgecombe, Rick P
2022-10-10 16:51 ` H.J. Lu
2022-10-12 12:29 ` Florian Weimer
2022-10-12 15:59 ` Dave Hansen
2022-10-12 16:54 ` Florian Weimer
2022-10-13 21:28 ` Edgecombe, Rick P
2022-10-13 22:15 ` H.J. Lu
2022-10-26 21:59 ` Edgecombe, Rick P
2022-09-29 22:28 ` [PATCH v2 02/39] x86/cet/shstk: Add Kconfig option for Shadow Stack Rick Edgecombe
2022-10-03 13:40 ` Kirill A . Shutemov
2022-10-03 19:53 ` Edgecombe, Rick P
2022-10-03 17:25 ` Kees Cook
2022-10-03 19:52 ` Edgecombe, Rick P
2022-10-03 19:42 ` Dave Hansen
2022-10-03 19:50 ` Edgecombe, Rick P
2022-10-12 20:04 ` Borislav Petkov
2022-10-13 0:31 ` Edgecombe, Rick P
2022-10-13 9:21 ` Borislav Petkov
2022-09-29 22:29 ` [PATCH v2 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks Rick Edgecombe
2022-10-03 17:26 ` Kees Cook
2022-10-14 16:20 ` Borislav Petkov
2022-10-14 19:35 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack Rick Edgecombe
2022-10-03 17:31 ` Kees Cook
2022-10-05 0:55 ` Andrew Cooper
2022-10-14 17:12 ` Borislav Petkov
2022-10-14 18:15 ` Edgecombe, Rick P
2022-10-14 19:44 ` Borislav Petkov
2022-09-29 22:29 ` [PATCH v2 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states Rick Edgecombe
2022-10-03 17:40 ` Kees Cook
2022-10-15 9:46 ` Borislav Petkov
2022-10-17 18:57 ` Edgecombe, Rick P
2022-10-17 19:33 ` Borislav Petkov
2022-09-29 22:29 ` [PATCH v2 06/39] x86/fpu: Add helper for modifying xstate Rick Edgecombe
2022-10-03 17:48 ` Kees Cook
2022-10-03 20:05 ` Edgecombe, Rick P
2022-10-04 4:05 ` Kees Cook
2022-10-04 14:18 ` Dave Hansen
2022-10-04 16:13 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 07/39] x86/cet: Add user control-protection fault handler Rick Edgecombe
2022-10-03 14:01 ` Kirill A . Shutemov
2022-10-03 18:12 ` Edgecombe, Rick P
2022-10-03 18:04 ` Kees Cook
2022-10-03 20:33 ` Edgecombe, Rick P
2022-10-03 22:51 ` Andy Lutomirski
2022-10-03 23:09 ` H. Peter Anvin
2022-10-03 23:11 ` Edgecombe, Rick P
2022-10-05 1:20 ` Andrew Cooper
2022-10-05 22:44 ` Edgecombe, Rick P
2022-10-05 9:39 ` Peter Zijlstra
2022-10-05 22:45 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages Rick Edgecombe
2022-10-03 14:17 ` Kirill A . Shutemov
2022-10-05 1:31 ` Andrew Cooper
2022-10-05 11:16 ` Peter Zijlstra
2022-10-05 12:34 ` Andrew Cooper
2022-09-29 22:29 ` [PATCH v2 09/39] x86/mm: Move pmd_write(), pud_write() up in the file Rick Edgecombe
2022-10-03 18:06 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 10/39] x86/mm: Introduce _PAGE_COW Rick Edgecombe
2022-09-30 15:16 ` Jann Horn
2022-10-06 16:10 ` Edgecombe, Rick P
2022-10-03 16:26 ` Kirill A . Shutemov
2022-10-03 21:36 ` Edgecombe, Rick P
2022-10-03 21:54 ` Jann Horn
2022-10-03 22:20 ` Edgecombe, Rick P
2022-10-03 22:14 ` Dave Hansen
2022-10-05 2:17 ` Andrew Cooper
2022-10-05 14:08 ` Dave Hansen
2022-10-05 23:06 ` Edgecombe, Rick P
2022-10-05 23:01 ` Edgecombe, Rick P
2022-10-05 11:33 ` Peter Zijlstra
2022-10-14 9:41 ` Peter Zijlstra
2022-10-14 15:52 ` Edgecombe, Rick P
2022-10-14 9:42 ` Peter Zijlstra
2022-10-14 18:06 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 11/39] x86/mm: Update pte_modify for _PAGE_COW Rick Edgecombe
2022-09-29 22:29 ` [PATCH v2 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW Rick Edgecombe
2022-10-03 17:43 ` Kirill A . Shutemov
2022-10-03 18:11 ` Nadav Amit
2022-10-03 18:51 ` Dave Hansen
2022-10-03 22:28 ` Edgecombe, Rick P
2022-10-03 23:17 ` Nadav Amit
2022-10-03 23:20 ` Nadav Amit
2022-10-03 23:25 ` Nadav Amit
2022-10-03 23:38 ` Edgecombe, Rick P
2022-10-04 0:40 ` Nadav Amit
2022-09-29 22:29 ` [PATCH v2 13/39] mm: Move VM_UFFD_MINOR_BIT from 37 to 38 Rick Edgecombe
2022-10-03 18:11 ` Kees Cook
2022-10-03 18:24 ` Peter Xu
2022-09-29 22:29 ` [PATCH v2 14/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory Rick Edgecombe
2022-10-03 17:47 ` Kirill A . Shutemov
2022-10-04 0:29 ` Edgecombe, Rick P
2022-10-03 18:17 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 15/39] x86/mm: Check Shadow Stack page fault errors Rick Edgecombe
2022-10-03 18:20 ` Kees Cook
2022-10-14 10:07 ` Peter Zijlstra
2022-10-14 15:51 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 16/39] x86/mm: Update maybe_mkwrite() for shadow stack Rick Edgecombe
2022-10-03 18:22 ` Kees Cook
2022-10-03 23:53 ` Kirill A . Shutemov
2022-10-14 15:32 ` Peter Zijlstra
2022-10-14 15:45 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 17/39] mm: Fixup places that call pte_mkwrite() directly Rick Edgecombe
2022-10-03 18:24 ` Kees Cook
2022-10-03 23:56 ` Kirill A . Shutemov
2022-10-04 16:15 ` Edgecombe, Rick P
2022-10-04 1:56 ` Nadav Amit
2022-10-04 16:21 ` Edgecombe, Rick P
2022-10-14 15:52 ` Peter Zijlstra
2022-10-14 15:56 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 18/39] mm: Add guard pages around a shadow stack Rick Edgecombe
2022-10-03 18:30 ` Kees Cook
2022-10-05 2:30 ` Andrew Cooper
2022-10-10 12:33 ` Florian Weimer
2022-10-10 13:32 ` Andrew Cooper
2022-10-10 13:40 ` Florian Weimer
2022-10-10 13:56 ` Andrew Cooper
2022-09-29 22:29 ` [PATCH v2 19/39] mm/mmap: Add shadow stack pages to memory accounting Rick Edgecombe
2022-10-03 18:31 ` Kees Cook
2022-10-04 0:03 ` Kirill A . Shutemov
2022-10-04 0:32 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 20/39] mm/mprotect: Exclude shadow stack from preserve_write Rick Edgecombe
2022-09-29 22:29 ` [PATCH v2 21/39] mm: Re-introduce vm_flags to do_mmap() Rick Edgecombe
2022-09-29 22:29 ` [PATCH v2 22/39] mm: Don't allow write GUPs to shadow stack memory Rick Edgecombe
2022-09-30 19:16 ` Dave Hansen
2022-09-30 20:30 ` Edgecombe, Rick P
2022-09-30 20:37 ` Dave Hansen
2022-09-30 23:00 ` Jann Horn
2022-09-30 23:02 ` Jann Horn
2022-09-30 23:04 ` Edgecombe, Rick P
2022-10-03 18:39 ` Kees Cook
2022-10-03 22:49 ` Andy Lutomirski
2022-10-04 4:21 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 23/39] x86: Introduce userspace API for CET enabling Rick Edgecombe
2022-10-03 19:01 ` Kees Cook
2022-10-03 22:51 ` Edgecombe, Rick P
2022-10-06 18:50 ` Mike Rapoport
2022-10-10 10:56 ` Florian Weimer
2022-10-10 16:28 ` Edgecombe, Rick P
2022-10-12 12:18 ` Florian Weimer
2022-10-12 17:30 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 24/39] x86/cet/shstk: Add user-mode shadow stack support Rick Edgecombe
2022-10-03 19:43 ` Kees Cook
2022-10-03 20:04 ` Dave Hansen
2022-10-04 4:04 ` Kees Cook
2022-10-04 16:25 ` Edgecombe, Rick P
2022-10-04 10:17 ` David Laight
2022-10-04 19:32 ` Kees Cook
2022-10-05 13:32 ` David Laight
2022-10-20 21:29 ` Edgecombe, Rick P
2022-10-20 22:54 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 25/39] x86/cet/shstk: Handle thread shadow stack Rick Edgecombe
2022-10-03 10:36 ` Mike Rapoport
2022-10-03 16:57 ` Edgecombe, Rick P
2022-10-03 20:29 ` Kees Cook
2022-10-04 22:09 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 26/39] x86/cet/shstk: Introduce routines modifying shstk Rick Edgecombe
2022-10-03 20:44 ` Kees Cook
2022-10-04 22:13 ` Edgecombe, Rick P
2022-10-05 2:43 ` Andrew Cooper
2022-10-05 22:47 ` Edgecombe, Rick P
2022-10-05 22:58 ` Andrew Cooper
2022-10-20 21:51 ` Edgecombe, Rick P
2022-09-29 22:29 ` [PATCH v2 27/39] x86/cet/shstk: Handle signals for shadow stack Rick Edgecombe
2022-10-03 20:52 ` Kees Cook
2022-10-20 22:08 ` Edgecombe, Rick P
2022-10-20 22:57 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 28/39] x86/cet/shstk: Introduce map_shadow_stack syscall Rick Edgecombe
2022-10-03 22:23 ` Kees Cook
2022-10-04 22:56 ` Edgecombe, Rick P
2022-10-04 23:16 ` H.J. Lu
2022-10-10 11:13 ` Florian Weimer
2022-10-10 14:19 ` Jason A. Donenfeld
2022-09-29 22:29 ` [PATCH v2 29/39] x86/cet/shstk: Support wrss for userspace Rick Edgecombe
2022-10-03 22:28 ` Kees Cook
2022-10-03 23:00 ` Andy Lutomirski
2022-10-04 4:37 ` Kees Cook
2022-10-06 0:38 ` Edgecombe, Rick P
2022-10-06 3:11 ` Kees Cook
2022-10-04 8:30 ` Mike Rapoport
2022-09-29 22:29 ` [PATCH v2 30/39] x86: Expose thread features status in /proc/$PID/arch_status Rick Edgecombe
2022-10-03 22:37 ` Kees Cook
2022-10-03 22:45 ` Andy Lutomirski
2022-10-04 4:18 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 31/39] x86/cet/shstk: Wire in CET interface Rick Edgecombe
2022-10-03 22:41 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 32/39] selftests/x86: Add shadow stack test Rick Edgecombe
2022-10-03 23:56 ` Kees Cook
2022-09-29 22:29 ` [PATCH v2 33/39] x86/cpufeatures: Limit shadow stack to Intel CPUs Rick Edgecombe
2022-10-03 23:57 ` Kees Cook
2022-10-04 0:09 ` Dave Hansen
2022-10-04 4:54 ` Kees Cook
2022-10-04 15:47 ` Nathan Chancellor
2022-10-04 19:43 ` John Allen
2022-10-04 20:34 ` Edgecombe, Rick P
2022-10-04 20:50 ` Nathan Chancellor
2022-10-04 21:17 ` H. Peter Anvin
2022-10-04 23:24 ` Edgecombe, Rick P
2022-11-03 17:39 ` John Allen [this message]
2022-10-20 21:22 ` Edgecombe, Rick P
2022-10-04 8:36 ` Mike Rapoport
2022-09-29 22:29 ` [OPTIONAL/CLEANUP v2 34/39] x86: Separate out x86_regset for 32 and 64 bit Rick Edgecombe
2022-09-29 22:29 ` [OPTIONAL/CLEANUP v2 35/39] x86: Improve formatting of user_regset arrays Rick Edgecombe
2022-09-29 22:29 ` [OPTIONAL/RFC v2 36/39] x86/fpu: Add helper for initing features Rick Edgecombe
2022-10-03 19:07 ` Chang S. Bae
2022-10-04 23:05 ` Edgecombe, Rick P
2022-09-29 22:29 ` [OPTIONAL/RFC v2 37/39] x86/cet: Add PTRACE interface for CET Rick Edgecombe
2022-10-03 23:59 ` Kees Cook
2022-10-04 8:44 ` Mike Rapoport
2022-10-04 19:24 ` Kees Cook
2022-09-29 22:29 ` [OPTIONAL/RFC v2 38/39] x86/cet/shstk: Add ARCH_CET_UNLOCK Rick Edgecombe
2022-10-04 0:00 ` Kees Cook
2022-09-29 22:29 ` [OPTIONAL/RFC v2 39/39] x86: Add alt shadow stack support Rick Edgecombe
2022-10-03 23:21 ` Andy Lutomirski
2022-10-04 16:12 ` Edgecombe, Rick P
2022-10-04 17:46 ` Andy Lutomirski
2022-10-04 18:04 ` Edgecombe, Rick P
2022-10-03 17:04 ` [PATCH v2 00/39] Shadowstacks for userspace Kees Cook
2022-10-03 17:25 ` Jann Horn
2022-10-04 5:01 ` Kees Cook
2022-10-04 9:57 ` David Laight
2022-10-04 19:28 ` Kees Cook
2022-10-03 18:33 ` Edgecombe, Rick P
2022-10-04 3:59 ` Kees Cook
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=67da8e11-c9b1-3445-bf7d-3854cea72b7e@amd.com \
--to=john.allen@amd.com \
--cc=arnd@arndb.de \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dethoma@microsoft.com \
--cc=eranian@google.com \
--cc=esyr@redhat.com \
--cc=fweimer@redhat.com \
--cc=gorcunov@gmail.com \
--cc=gustavoars@kernel.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jamorris@linux.microsoft.com \
--cc=jannh@google.com \
--cc=joao.moreira@intel.com \
--cc=kcc@google.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=weijiang.yang@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;
as well as URLs for NNTP newsgroup(s).