linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"Szabolcs.Nagy@arm.com" <Szabolcs.Nagy@arm.com>,
	"brauner@kernel.org" <brauner@kernel.org>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"debug@rivosinc.com" <debug@rivosinc.com>,
	"mgorman@suse.de" <mgorman@suse.de>,
	"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
	"fweimer@redhat.com" <fweimer@redhat.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"vschneid@redhat.com" <vschneid@redhat.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"bp@alien8.de" <bp@alien8.de>,
	"bsegall@google.com" <bsegall@google.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"juri.lelli@redhat.com" <juri.lelli@redhat.com>
Cc: "yury.khrustalev@arm.com" <yury.khrustalev@arm.com>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"jannh@google.com" <jannh@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"wilco.dijkstra@arm.com" <wilco.dijkstra@arm.com>,
	"kees@kernel.org" <kees@kernel.org>
Subject: Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
Date: Tue, 20 Aug 2024 21:36:46 +0000	[thread overview]
Message-ID: <dc8328dbaa01ca7443eeb75024752c673904e3a4.camel@intel.com> (raw)
In-Reply-To: <20240819-clone3-shadow-stack-v9-4-962d74f99464@kernel.org>

On Mon, 2024-08-19 at 20:24 +0100, Mark Brown wrote:


[snip]

>  
> diff --git a/arch/x86/kernel/shstk.c b/arch/x86/kernel/shstk.c
> index 059685612362..42b2b18de20d 100644
> --- a/arch/x86/kernel/shstk.c
> +++ b/arch/x86/kernel/shstk.c
> @@ -191,44 +191,103 @@ void reset_thread_features(void)
>         current->thread.features_locked = 0;
>  }
>  
> -unsigned long shstk_alloc_thread_stack(struct task_struct *tsk, unsigned long
> clone_flags,
> -                                      unsigned long stack_size)
> +int arch_shstk_validate_clone(struct task_struct *t,
> +                             struct vm_area_struct *vma,
> +                             struct page *page,
> +                             struct kernel_clone_args *args)
> +{
> +       /*
> +        * SSP is aligned, so reserved bits and mode bit are a zero, just mark
> +        * the token 64-bit.
> +        */
> +       void *maddr = kmap_local_page(page);
> +       int offset;
> +       unsigned long addr, ssp;
> +       u64 expected;
> +       u64 val;
> +
> +       if (!features_enabled(ARCH_SHSTK_SHSTK))
> +               return 0;
> +
> +       ssp = args->shadow_stack + args->shadow_stack_size;
> +       addr = ssp - SS_FRAME_SIZE;
> +       expected = ssp | BIT(0);
> +       offset = offset_in_page(ssp);
> +
> +       /* This should really be an atomic cmpxchg.  It is not. */
> +       copy_from_user_page(vma, page, addr, &val, maddr + offset,
> +                           sizeof(val));

Were so close to the real cmpxchg at this point. I took a shot at it with the
diff at the end. I'm not sure if it might need some of the instrumentation
calls.

> +
> +       if (val != expected)
> +               return false;

Return false for an int will be 0 (i.e. success). I think it might be covering
up a bug. The gup happens to args->shadow_stack + args->shadow_stack_size - 1
(the size inclusive). But the copy happens at the size exclusive.

So shadow_stack_size = PAGE_SIZE, will try to read the token at the start of the
shadow stack, but the failure will be reported as success. I think...

On another note, I think we need to verify that ssp is 8 byte aligned, or it
could be made to overflow the adjacent direct map page a few bytes. At least I
didn't see how it was prevented.

> +       val = 0;
> +
> +       copy_to_user_page(vma, page, addr, maddr + offset, &val, sizeof(val));
> +       set_page_dirty_lock(page);
> +
> +       return 0;
> +}
> +
> 
[snip]
>  
> +static int shstk_validate_clone(struct task_struct *p,
> +                               struct kernel_clone_args *args)
> +{
> +       struct mm_struct *mm;
> +       struct vm_area_struct *vma;
> +       struct page *page;
> +       unsigned long addr;
> +       int ret;
> +
> +       if (!IS_ENABLED(CONFIG_ARCH_HAS_USER_SHADOW_STACK))
> +               return 0;
> +
> +       if (!args->shadow_stack)
> +               return 0;
> +
> +       mm = get_task_mm(p);
> +       if (!mm)
> +               return -EFAULT;
> +
> +       mmap_read_lock(mm);
> +
> +       /*
> +        * All current shadow stack architectures have tokens at the
> +        * top of a downward growing shadow stack.
> +        */
> +       addr = args->shadow_stack + args->shadow_stack_size - 1;
> +       addr = untagged_addr_remote(mm, addr);
> +
> +       page = get_user_page_vma_remote(mm, addr, FOLL_FORCE | FOLL_WRITE,
> +                                       &vma);
> +       if (IS_ERR(page)) {
> +               ret = -EFAULT;
> +               goto out;
> +       }
> +
> +       if (!(vma->vm_flags & VM_SHADOW_STACK)) {

Can we check VM_WRITE here too? At least on x86, shadow stacks can be
mprotect()ed as read-only. The reason for this before I think fell out of the
implementation details, but all the same it would be nice be consistent. Then it
should behave identically to a real shadow stack access.

> +               ret = -EFAULT;
> +               goto out_page;
> +       }
> +
> +       ret = arch_shstk_validate_clone(p, vma, page, args);
> +
> +out_page:
> +       put_page(page);
> +out:
> +       mmap_read_unlock(mm);
> +       mmput(mm);
> +       return ret;
> +}
> +
> 
[snip]
>  
> +/**
> + * clone3_shadow_stack_valid - check and prepare shadow stack
> + * @kargs: kernel clone args
> + *
> + * Verify that shadow stacks are only enabled if supported.
> + */
> +static inline bool clone3_shadow_stack_valid(struct kernel_clone_args *kargs)
> +{
> +       if (kargs->shadow_stack) {
> +               if (!kargs->shadow_stack_size)
> +                       return false;
> +
> +               if (kargs->shadow_stack_size < SHADOW_STACK_SIZE_MIN)
> +                       return false;
> +
> +               if (kargs->shadow_stack_size > rlimit(RLIMIT_STACK))
> +                       return false;

At the risk of asking a stupid question or one that I should have asked a long
time ago...

Why do we need both shadow_stack and shadow_stack_size? We are basically asking
it to consume a token at a pointer and have userspace manage the shadow stack
itself. So why does the kernel care what size it is? Couldn't we just have
'shadow_stack' have that mean consume a token here.

> +
> +               /*
> +                * The architecture must check support on the specific
> +                * machine.
> +                */
> +               return IS_ENABLED(CONFIG_ARCH_HAS_USER_SHADOW_STACK);
> +       } else {
> +               return !kargs->shadow_stack_size;
> +       }
> +}
> +

Fixing some of mentioned bugs, this on top passed the selftests for me. It
doesn't have the 8 byte alignment check I mentioned because I'm less sure I
might be missing it somewhere.

diff --git a/arch/x86/kernel/shstk.c b/arch/x86/kernel/shstk.c
index 42b2b18de20d..2685180b8c5c 100644
--- a/arch/x86/kernel/shstk.c
+++ b/arch/x86/kernel/shstk.c
@@ -204,7 +204,6 @@ int arch_shstk_validate_clone(struct task_struct *t,
        int offset;
        unsigned long addr, ssp;
        u64 expected;
-       u64 val;
 
        if (!features_enabled(ARCH_SHSTK_SHSTK))
                return 0;
@@ -212,17 +211,12 @@ int arch_shstk_validate_clone(struct task_struct *t,
        ssp = args->shadow_stack + args->shadow_stack_size;
        addr = ssp - SS_FRAME_SIZE;
        expected = ssp | BIT(0);
-       offset = offset_in_page(ssp);
+       offset = offset_in_page(addr);
 
-       /* This should really be an atomic cmpxchg.  It is not. */
-       copy_from_user_page(vma, page, addr, &val, maddr + offset,
-                           sizeof(val));
+       if (!cmpxchg_to_user_page(vma, page, addr, (unsigned long *)(maddr +
offset),
+                                 expected, 0))
+               return -EINVAL;
 
-       if (val != expected)
-               return false;
-       val = 0;
-
-       copy_to_user_page(vma, page, addr, maddr + offset, &val, sizeof(val));
        set_page_dirty_lock(page);
 
        return 0;
diff --git a/include/asm-generic/cacheflush.h b/include/asm-generic/cacheflush.h
index 7ee8a179d103..1500d49bc3f7 100644
--- a/include/asm-generic/cacheflush.h
+++ b/include/asm-generic/cacheflush.h
@@ -124,4 +124,15 @@ static inline void flush_cache_vunmap(unsigned long start,
unsigned long end)
        } while (0)
 #endif
 
+#ifndef cmpxchg_to_user_page
+#define cmpxchg_to_user_page(vma, page, vaddr, ptr, old, new)  \
+({                                                             \
+       bool ret;                                               \
+                                                               \
+       ret = try_cmpxchg(ptr, &old, new);                      \
+       flush_icache_user_page(vma, page, vaddr, sizeof(*ptr)); \
+       ret;                                                    \
+})
+#endif
+
 #endif /* _ASM_GENERIC_CACHEFLUSH_H */


  reply	other threads:[~2024-08-20 21:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 19:24 [PATCH RFT v9 0/8] fork: Support shadow stacks in clone3() Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 1/8] Documentation: userspace-api: Add shadow stack API documentation Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 2/8] selftests: Provide helper header for shadow stack testing Mark Brown
2024-08-20 21:36   ` Edgecombe, Rick P
2024-08-19 19:24 ` [PATCH RFT v9 3/8] mm: Introduce ARCH_HAS_USER_SHADOW_STACK Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3() Mark Brown
2024-08-20 21:36   ` Edgecombe, Rick P [this message]
2024-08-20 23:34     ` Mark Brown
2024-08-20 23:57       ` Edgecombe, Rick P
2024-08-21  0:19         ` Mark Brown
2024-08-21  1:45           ` Edgecombe, Rick P
2024-08-21 12:45             ` Mark Brown
2024-08-21 15:54               ` Edgecombe, Rick P
2024-08-21 17:23                 ` Mark Brown
2024-08-21 18:05                   ` Catalin Marinas
2024-09-27  8:50                   ` Christian Brauner
2024-09-27 15:21                     ` Edgecombe, Rick P
2024-10-01 15:12                       ` Christian Brauner
2024-10-01 17:33                         ` Mark Brown
2024-10-01 23:03                           ` Edgecombe, Rick P
2024-10-02 13:42                             ` Mark Brown
2024-10-02 21:01                               ` Mark Brown
2024-10-02 21:25                                 ` Edgecombe, Rick P
2024-10-03 16:05                         ` Yury Khrustalev
2024-08-19 19:24 ` [PATCH RFT v9 5/8] selftests/clone3: Remove redundant flushes of output streams Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 6/8] selftests/clone3: Factor more of main loop into test_clone3() Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code Mark Brown
2024-08-19 19:24 ` [PATCH RFT v9 8/8] selftests/clone3: Test shadow stack support Mark Brown

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=dc8328dbaa01ca7443eeb75024752c673904e3a4.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=bp@alien8.de \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=bsegall@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=debug@rivosinc.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jannh@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kees@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=wilco.dijkstra@arm.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yury.khrustalev@arm.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).