From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "debug@rivosinc.com" <debug@rivosinc.com>,
"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"lorenzo.stoakes@oracle.com" <lorenzo.stoakes@oracle.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"arnd@arndb.de" <arnd@arndb.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH RFC/RFT v2 1/2] mm: helper `is_shadow_stack_vma` to check shadow stack vma
Date: Fri, 1 Nov 2024 21:47:25 +0000 [thread overview]
Message-ID: <5a89e49fe1f9d6ee2c72af411d40e2dbb1299759.camel@intel.com> (raw)
In-Reply-To: <20241016-shstk_converge-v2-1-c41536eb5c3b@rivosinc.com>
On Wed, 2024-10-16 at 14:57 -0700, Deepak Gupta wrote:
> VM_SHADOW_STACK (alias to VM_HIGH_ARCH_5) is used to encode shadow stack
> VMA on three architectures (x86 shadow stack, arm GCS and RISC-V shadow
> stack). In case architecture doesn't implement shadow stack, it's VM_NONE
> Introducing a helper `is_shadow_stack_vma` to determine shadow stack vma
> or not.
I don't understand why we need this. IIRC was some discussion about wanting to
abstract different ways of testing for shadow stack VMAs for different
architectures since risc-v was going to do it differently. But now this says
they are all the same, so what's wrong with the open coded check?
>
> Signed-off-by: Deepak Gupta <debug@rivosinc.com>
> ---
> mm/gup.c | 2 +-
> mm/mmap.c | 2 +-
> mm/vma.h | 10 +++++++---
> 3 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/mm/gup.c b/mm/gup.c
> index a82890b46a36..8e6e14179f6c 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -1282,7 +1282,7 @@ static int check_vma_flags(struct vm_area_struct *vma, unsigned long gup_flags)
> !writable_file_mapping_allowed(vma, gup_flags))
> return -EFAULT;
>
> - if (!(vm_flags & VM_WRITE) || (vm_flags & VM_SHADOW_STACK)) {
> + if (!(vm_flags & VM_WRITE) || is_shadow_stack_vma(vm_flags)) {
> if (!(gup_flags & FOLL_FORCE))
> return -EFAULT;
> /* hugetlb does not support FOLL_FORCE|FOLL_WRITE. */
> diff --git a/mm/mmap.c b/mm/mmap.c
> index dd4b35a25aeb..0853e6784069 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -708,7 +708,7 @@ static unsigned long unmapped_area_topdown(struct vm_unmapped_area_info *info)
> */
> static inline unsigned long stack_guard_placement(vm_flags_t vm_flags)
> {
> - if (vm_flags & VM_SHADOW_STACK)
> + if (is_shadow_stack_vma(vm_flags))
> return PAGE_SIZE;
>
> return 0;
> diff --git a/mm/vma.h b/mm/vma.h
> index 819f994cf727..0f238dc37231 100644
> --- a/mm/vma.h
> +++ b/mm/vma.h
> @@ -357,7 +357,7 @@ static inline struct vm_area_struct *vma_prev_limit(struct vma_iterator *vmi,
> }
>
> /*
> - * These three helpers classifies VMAs for virtual memory accounting.
> + * These four helpers classifies VMAs for virtual memory accounting.
> */
>
> /*
> @@ -368,6 +368,11 @@ static inline bool is_exec_mapping(vm_flags_t flags)
> return (flags & (VM_EXEC | VM_WRITE | VM_STACK)) == VM_EXEC;
> }
>
> +static inline bool is_shadow_stack_vma(vm_flags_t vm_flags)
> +{
> + return !!(vm_flags & VM_SHADOW_STACK);
> +}
> +
> /*
> * Stack area (including shadow stacks)
> *
> @@ -376,7 +381,7 @@ static inline bool is_exec_mapping(vm_flags_t flags)
> */
> static inline bool is_stack_mapping(vm_flags_t flags)
> {
> - return ((flags & VM_STACK) == VM_STACK) || (flags & VM_SHADOW_STACK);
> + return ((flags & VM_STACK) == VM_STACK) || is_shadow_stack_vma(flags);
> }
>
> /*
> @@ -387,7 +392,6 @@ static inline bool is_data_mapping(vm_flags_t flags)
> return (flags & (VM_WRITE | VM_SHARED | VM_STACK)) == VM_WRITE;
> }
>
> -
> static inline void vma_iter_config(struct vma_iterator *vmi,
> unsigned long index, unsigned long last)
> {
>
next prev parent reply other threads:[~2024-11-01 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 21:57 [PATCH RFC/RFT v2 0/2] Converge common flows for cpu assisted shadow stack Deepak Gupta
2024-10-16 21:57 ` [PATCH RFC/RFT v2 1/2] mm: helper `is_shadow_stack_vma` to check shadow stack vma Deepak Gupta
2024-10-17 11:22 ` Mark Brown
2024-10-19 1:24 ` Deepak Gupta
2024-11-01 21:47 ` Edgecombe, Rick P [this message]
2024-11-14 23:20 ` Deepak Gupta
2024-10-16 21:57 ` [PATCH RFC/RFT v2 2/2] kernel: converge common shadow stack flow agnostic to arch Deepak Gupta
2024-11-01 21:50 ` Edgecombe, Rick P
2024-11-01 22:39 ` Mark Brown
2024-11-14 23:30 ` Deepak Gupta
2024-11-14 23:33 ` Edgecombe, Rick P
2024-11-01 21:47 ` [PATCH RFC/RFT v2 0/2] Converge common flows for cpu assisted shadow stack Edgecombe, Rick P
2024-11-14 23:15 ` Deepak Gupta
2024-11-15 14:17 ` 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=5a89e49fe1f9d6ee2c72af411d40e2dbb1299759.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=debug@rivosinc.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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