From: Jeff Xu <jeffxu@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, keescook@chromium.org, corbet@lwn.net,
jorgelo@chromium.org, groeck@chromium.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, jannh@google.com, sroettger@google.com,
pedro.falcato@gmail.com, linux-hardening@vger.kernel.org,
willy@infradead.org, gregkh@linuxfoundation.org,
torvalds@linux-foundation.org, deraadt@openbsd.org,
usama.anjum@collabora.com, surenb@google.com,
merimus@google.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, enh@google.com
Subject: Re: [PATCH] mseal.rst additional fix
Date: Thu, 10 Oct 2024 17:23:06 -0700 [thread overview]
Message-ID: <CABi2SkXecdseZBeEJOeP8boP7aEAf815-1H6eMHDy=a4d1oXMg@mail.gmail.com> (raw)
In-Reply-To: <5e1ef8a0-f063-4166-9d93-cf047cdd2792@infradead.org>
On Tue, Oct 8, 2024 at 9:37 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
>
>
> On 10/7/24 9:18 PM, jeffxu@chromium.org wrote:
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > Change "overwrite" to overwrites"
> >
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> > ---
> > Documentation/userspace-api/mseal.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/userspace-api/mseal.rst b/Documentation/userspace-api/mseal.rst
> > index 41102f74c5e2..54bbcce330ec 100644
> > --- a/Documentation/userspace-api/mseal.rst
> > +++ b/Documentation/userspace-api/mseal.rst
> > @@ -97,7 +97,7 @@ Blocked mm syscall for sealed mapping
> > The first set of syscalls to block is munmap, mremap, mmap. They can
> > either leave an empty space in the address space, therefore allowing
> > replacement with a new mapping with new set of attributes, or can
> > - overwrite the existing mapping with another mapping.
> > + overwrites the existing mapping with another mapping.
>
> No, that one is correct as is.
>
Ah, yes. Please ignore this additional patch.
> >
> > mprotect and pkey_mprotect are blocked because they changes the
> > protection bits (RWX) of the mapping.
>
> --
> ~Randy
next prev parent reply other threads:[~2024-10-11 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 4:09 [PATCH v3 0/1] update mseal.rst jeffxu
2024-10-08 4:09 ` [PATCH v3 1/1] mseal: " jeffxu
2024-10-08 4:18 ` [PATCH] mseal.rst additional fix jeffxu
2024-10-08 16:37 ` Randy Dunlap
2024-10-11 0:23 ` Jeff Xu [this message]
2024-10-08 17:48 ` [PATCH v3 1/1] mseal: update mseal.rst Pedro Falcato
2024-10-15 20:00 ` 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='CABi2SkXecdseZBeEJOeP8boP7aEAf815-1H6eMHDy=a4d1oXMg@mail.gmail.com' \
--to=jeffxu@chromium.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=deraadt@openbsd.org \
--cc=enh@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jannh@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=merimus@google.com \
--cc=pedro.falcato@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sroettger@google.com \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=usama.anjum@collabora.com \
--cc=willy@infradead.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