From: Jeff Xu <jeffxu@chromium.org>
To: Jann Horn <jannh@google.com>
Cc: akpm@linux-foundation.org, sroettger@google.com,
rdunlap@infradead.org, david@redhat.com,
adhemerval.zanella@linaro.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, jorgelo@chromium.org, keescook@chromium.org
Subject: Re: [PATCH v1 1/1] /proc/pid/smaps: add mseal info for vma
Date: Fri, 14 Jun 2024 12:06:10 -0700 [thread overview]
Message-ID: <CABi2SkXrK5TkQZOvekjevQiMFhPWrVXyEAVRkjs5m6Xg8ncDXw@mail.gmail.com> (raw)
In-Reply-To: <CAG48ez0c3PyXhaW78tCXW0_e45YJtfOGj=shKZrLu5RZJ66vGg@mail.gmail.com>
On Fri, Jun 14, 2024 at 11:43 AM Jann Horn <jannh@google.com> wrote:
>
> Hi!
>
> On Fri, Jun 14, 2024 at 8:24 PM <jeffxu@chromium.org> wrote:
> > 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
>
> Nit: Why "page"? The sealing is a property of the VMA, not of the
> pages mapped into it. Maybe "sealed area" and an abbreviation like
> "sl" would make sense?
>
ok. Maybe just sealed for short:
sl "sealed"
Thanks
-Jeff
prev parent reply other threads:[~2024-06-14 19:06 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 ` [PATCH v1 1/1] /proc/pid/smaps: add mseal info for vma jeffxu
2024-06-14 18:42 ` Jann Horn
2024-06-14 19:00 ` Jeff Xu
2024-06-14 19:06 ` Jeff Xu [this message]
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=CABi2SkXrK5TkQZOvekjevQiMFhPWrVXyEAVRkjs5m6Xg8ncDXw@mail.gmail.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