From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sroettger@google.com,rdunlap@infradead.org,keescook@chromium.org,jorgelo@chromium.org,jannh@google.com,david@redhat.com,adhemerval.zanella@linaro.org,jeffxu@chromium.org,akpm@linux-foundation.org
Subject: + proc-pid-smaps-add-mseal-info-for-vma.patch added to mm-hotfixes-unstable branch
Date: Fri, 14 Jun 2024 18:12:36 -0700 [thread overview]
Message-ID: <20240615011237.6ED42C2BD10@smtp.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3864 bytes --]
The patch titled
Subject: /proc/pid/smaps: add mseal info for vma
has been added to the -mm mm-hotfixes-unstable branch. Its filename is
proc-pid-smaps-add-mseal-info-for-vma.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/proc-pid-smaps-add-mseal-info-for-vma.patch
This patch will later appear in the mm-hotfixes-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Jeff Xu <jeffxu@chromium.org>
Subject: /proc/pid/smaps: add mseal info for vma
Date: Fri, 14 Jun 2024 23:20:14 +0000
Add sl in /proc/pid/smaps to indicate vma is sealed
Link: https://lkml.kernel.org/r/20240614232014.806352-2-jeffxu@google.com
Fixes: 8be7258aad44 ("mseal: add mseal syscall")
Signed-off-by: Jeff Xu <jeffxu@chromium.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: David Hildenbrand <david@redhat.com>
Cc: Jann Horn <jannh@google.com>
Cc: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Röttger <sroettger@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.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(-)
--- a/Documentation/filesystems/proc.rst~proc-pid-smaps-add-mseal-info-for-vma
+++ a/Documentation/filesystems/proc.rst
@@ -571,6 +571,7 @@ encoded manner. The codes are the follow
um userfaultfd missing tracking
uw userfaultfd wr-protect tracking
ss shadow stack page
+ sl sealed
== =======================================
Note that there is no guarantee that every flag and associated mnemonic will
--- a/fs/proc/task_mmu.c~proc-pid-smaps-add-mseal-info-for-vma
+++ a/fs/proc/task_mmu.c
@@ -707,6 +707,9 @@ static void show_smap_vma_flags(struct s
#ifdef CONFIG_X86_USER_SHADOW_STACK
[ilog2(VM_SHADOW_STACK)] = "ss",
#endif
+#ifdef CONFIG_64BIT
+ [ilog2(VM_SEALED)] = "sl",
+#endif
};
size_t i;
--- a/include/linux/mm.h~proc-pid-smaps-add-mseal-info-for-vma
+++ a/include/linux/mm.h
@@ -406,6 +406,11 @@ extern unsigned int kobjsize(const void
#define VM_ALLOW_ANY_UNCACHED VM_NONE
#endif
+#ifdef CONFIG_64BIT
+/* VM is sealed, in vm_flags */
+#define VM_SEALED _BITUL(63)
+#endif
+
/* Bits set in the VMA until the stack is in its final location */
#define VM_STACK_INCOMPLETE_SETUP (VM_RAND_READ | VM_SEQ_READ | VM_STACK_EARLY)
--- a/mm/internal.h~proc-pid-smaps-add-mseal-info-for-vma
+++ a/mm/internal.h
@@ -1435,11 +1435,6 @@ unsigned long shrink_slab(gfp_t gfp_mask
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)
{
if (flags)
_
Patches currently in -mm which might be from jeffxu@chromium.org are
mm-memfd-add-documentation-for-mfd_noexec_seal-mfd_exec.patch
mm-memfd-add-documentation-for-mfd_noexec_seal-mfd_exec-v2.patch
mm-memfd-add-documentation-for-mfd_noexec_seal-mfd_exec-v3.patch
proc-pid-smaps-add-mseal-info-for-vma.patch
reply other threads:[~2024-06-15 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240615011237.6ED42C2BD10@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=adhemerval.zanella@linaro.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.