| Message ID | 20241008041804.1481453-1-jeffxu@chromium.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | mseal.rst additional fix | expand |
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. > > mprotect and pkey_mprotect are blocked because they changes the > protection bits (RWX) of the mapping.
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
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. mprotect and pkey_mprotect are blocked because they changes the protection bits (RWX) of the mapping.