Re: [PATCH v4 16/30] riscv/shstk: If needed allocate a new shadow stack on clone

ux/commits/Deepak-Gupta/mm-Introduce-ARCH_HAS_USER_SHADOW_STACK/20240913-072124 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/20240912231650.3740732-17-debug%40rivosinc.com patch subject: [PATCH v4 16/30] riscv/shstk:

Re: [PATCH v4 16/30] riscv/shstk: If needed allocate a new shadow stack on clone

ux/commits/Deepak-Gupta/mm-Introduce-ARCH_HAS_USER_SHADOW_STACK/20240913-072124 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/20240912231650.3740732-17-debug%40rivosinc.com patch subject: [PATCH v4 16/30] riscv/shstk:

Re: [PATCH v4 16/30] riscv/shstk: If needed allocate a new shadow stack on clone

k-Gupta/mm-Introduce-ARCH_HAS_USER_SHADOW_STACK/20240913-072124 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/20240912231650.3740732-17-debug%40rivosinc.com patch subject: [PATCH v4 16/30] riscv/shstk: If needed allocate a

[PATCH v4 16/30] riscv/shstk: If needed allocate a new shadow stack on clone

Userspace specifies CLONE_VM to share address space and spawn new thread. `clone` allow userspace to specify a new stack for new thread. However there is no way to specify new shadow stack base address without changing API. This patch allocates a new shadow stack whenever CLONE_VM is given. In cas