From: jeffxu@chromium.org
To: akpm@linux-foundation.org, jannh@google.com,
sroettger@google.com, rdunlap@infradead.org, david@redhat.com,
adhemerval.zanella@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
jorgelo@chromium.org, keescook@chromium.org,
Jeff Xu <jeffxu@chromium.org>
Subject: [PATCH v1 1/1] /proc/pid/smaps: add mseal info for vma
Date: Fri, 14 Jun 2024 18:23:27 +0000 [thread overview]
Message-ID: <20240614182327.752156-2-jeffxu@google.com> (raw)
In-Reply-To: <20240614182327.752156-1-jeffxu@google.com>
From: Jeff Xu <jeffxu@chromium.org>
Add sp in /proc/pid/smaps to indicate vma is sealed
Signed-off-by: Jeff Xu <jeffxu@chromium.org>
---
Documentation/filesystems/proc.rst | 1 +
fs/proc/task_mmu.c | 3 +++
include/linux/mm.h | 5 +++++
mm/internal.h | 5 -----
4 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 7c3a565ffbef..400217a1589c 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -571,6 +571,7 @@ encoded manner. The codes are the following:
um userfaultfd missing tracking
uw userfaultfd wr-protect tracking
ss shadow stack page
+ sp sealed page
== =======================================
Note that there is no guarantee that every flag and associated mnemonic will
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index 6ed1f56b32b4..ba2db75ca22a 100644
--- a/fs/proc/task_mmu.c
+++ b/fs/proc/task_mmu.c
@@ -711,6 +711,9 @@ static void show_smap_vma_flags(struct seq_file *m, struct vm_area_struct *vma)
#endif /* CONFIG_HAVE_ARCH_USERFAULTFD_MINOR */
#ifdef CONFIG_X86_USER_SHADOW_STACK
[ilog2(VM_SHADOW_STACK)] = "ss",
+#endif
+#ifdef CONFIG_64BIT
+ [ilog2(VM_SEALED)] = "sp",
#endif
};
size_t i;
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 587d34879865..8600564898fa 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -314,6 +314,11 @@ extern unsigned int kobjsize(const void *objp);
#define VM_NOHUGEPAGE 0x40000000 /* MADV_NOHUGEPAGE marked this vma */
#define VM_MERGEABLE 0x80000000 /* KSM may merge identical pages */
+#ifdef CONFIG_64BIT
+/* VM is sealed, in vm_flags */
+#define VM_SEALED _BITUL(63)
+#endif
+
#ifdef CONFIG_ARCH_USES_HIGH_VMA_FLAGS
#define VM_HIGH_ARCH_BIT_0 32 /* bit only usable on 64-bit architectures */
#define VM_HIGH_ARCH_BIT_1 33 /* bit only usable on 64-bit architectures */
diff --git a/mm/internal.h b/mm/internal.h
index fd68c43664d5..72f7c110d563 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -1509,11 +1509,6 @@ void __meminit __init_single_page(struct page *page, unsigned long pfn,
unsigned long shrink_slab(gfp_t gfp_mask, int nid, struct mem_cgroup *memcg,
int priority);
-#ifdef CONFIG_64BIT
-/* VM is sealed, in vm_flags */
-#define VM_SEALED _BITUL(63)
-#endif
-
#ifdef CONFIG_64BIT
static inline int can_do_mseal(unsigned long flags)
{
--
2.45.2.627.g7a2c4fd464-goog
next prev parent reply other threads:[~2024-06-14 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 18:23 [PATCH v1 0/1] add mseal to /proc/pid/smaps jeffxu
2024-06-14 18:23 ` jeffxu [this message]
2024-06-14 18:42 ` [PATCH v1 1/1] /proc/pid/smaps: add mseal info for vma Jann Horn
2024-06-14 19:00 ` Jeff Xu
2024-06-14 19:06 ` Jeff Xu
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=20240614182327.752156-2-jeffxu@google.com \
--to=jeffxu@chromium.org \
--cc=adhemerval.zanella@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sroettger@google.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