[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241008040942.1478931-1-jeffxu@chromium.org>
Date: Tue, 8 Oct 2024 04:09:40 +0000
From: jeffxu@...omium.org
To: akpm@...ux-foundation.org,
keescook@...omium.org,
corbet@....net
Cc: jorgelo@...omium.org,
groeck@...omium.org,
linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
linux-mm@...ck.org,
jannh@...gle.com,
sroettger@...gle.com,
pedro.falcato@...il.com,
linux-hardening@...r.kernel.org,
willy@...radead.org,
gregkh@...uxfoundation.org,
torvalds@...ux-foundation.org,
deraadt@...nbsd.org,
usama.anjum@...labora.com,
surenb@...gle.com,
merimus@...gle.com,
rdunlap@...radead.org,
lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com,
enh@...gle.com,
Jeff Xu <jeffxu@...omium.org>
Subject: [PATCH v3 0/1] update mseal.rst
From: Jeff Xu <jeffxu@...omium.org>
Pedro Falcato's optimization [1] for checking sealed VMAs, which replaces
the can_modify_mm() function with an in-loop check, necessitates an update
to the mseal.rst documentation to reflect this change.
Furthermore, the document has received offline comments regarding the code
sample and suggestions for sentence clarification to enhance reader
comprehension.
[1] https://lore.kernel.org/linux-mm/20240817-mseal-depessimize-v3-0-d8d2e037df30@gmail.com/
History:
V3: update according to Randy Dunlap's comment
V2: update according to Randy Dunlap's comments.
https://lore.kernel.org/all/20241001002628.2239032-1-jeffxu@chromium.org/
V1: initial version
https://lore.kernel.org/all/20240927185211.729207-1-jeffxu@chromium.org/
Jeff Xu (1):
mseal: update mseal.rst
Documentation/userspace-api/mseal.rst | 307 +++++++++++++-------------
1 file changed, 148 insertions(+), 159 deletions(-)
--
2.47.0.rc0.187.ge670bccf7e-goog
Powered by blists - more mailing lists