From: David Hildenbrand <david@redhat.com>
To: wangfushuai <wangfushuai@baidu.com>,
akpm@linux-foundation.org, andrii@kernel.org, osalvador@suse.de,
Liam.Howlett@Oracle.com, christophe.leroy@csgroup.eu
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fs/proc/task_mmu: add VM_SHADOW_STACK for arm64 when support GCS
Date: Sat, 7 Jun 2025 20:17:01 +0200 [thread overview]
Message-ID: <ebaa1561-eb42-43f6-ba33-e59982f6b359@redhat.com> (raw)
In-Reply-To: <20250607131525.76746-1-wangfushuai@baidu.com>
On 07.06.25 15:15, wangfushuai wrote:
> The recent commit adding VM_SHADOW_STACK for arm64 GCS did not update
> the /proc/[pid]/smaps display logic to show the "ss" flag for GCS pages.
> This patch adds the necessary condition to display "ss" flag.
>
> Fixes: ae80e1629aea ("mm: Define VM_SHADOW_STACK for arm64 when we support GCS")
> Signed-off-by: wangfushuai <wangfushuai@baidu.com>
> ---
> fs/proc/task_mmu.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> index 27972c0749e7..2c2ee893a797 100644
> --- a/fs/proc/task_mmu.c
> +++ b/fs/proc/task_mmu.c
> @@ -994,6 +994,9 @@ static void show_smap_vma_flags(struct seq_file *m, struct vm_area_struct *vma)
> #ifdef CONFIG_ARCH_HAS_USER_SHADOW_STACK
> [ilog2(VM_SHADOW_STACK)] = "ss",
> #endif
> +#if defined(CONFIG_ARM64_GCS)
> + [ilog2(VM_SHADOW_STACK)] = "ss",
> +#endif
Which makes me wonder why we don't select
CONFIG_ARCH_HAS_USER_SHADOW_STACK for CONFIG_ARM64_GCS?
> #if defined(CONFIG_64BIT) || defined(CONFIG_PPC32)
> [ilog2(VM_DROPPABLE)] = "dp",
> #endif
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-06-07 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 13:15 wangfushuai
2025-06-07 18:17 ` David Hildenbrand [this message]
2025-06-07 21:31 ` Andrew Morton
2025-06-08 7:35 ` wangfushuai
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=ebaa1561-eb42-43f6-ba33-e59982f6b359@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=wangfushuai@baidu.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
all inboxes | Powered by JetHome®