From: Pedro Falcato <pedro.falcato@gmail.com>
To: jeffxu@chromium.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,
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, rdunlap@infradead.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
enh@google.com
Subject: Re: [PATCH v3 1/1] mseal: update mseal.rst
Date: Tue, 8 Oct 2024 18:48:03 +0100 [thread overview]
Message-ID: <CAKbZUD1uyzhS6C0T_F_U+4gfuOcHFMJ-82XsFaLZQj91F-BKZw@mail.gmail.com> (raw)
In-Reply-To: <20241008040942.1478931-2-jeffxu@chromium.org>
On Tue, Oct 8, 2024 at 5:09 AM <jeffxu@chromium.org> wrote:
>
> From: Jeff Xu <jeffxu@chromium.org>
>
> Update doc after in-loop change: mprotect/madvise can have
> partially updated and munmap is atomic.
>
> Fix indentation and clarify some sections to improve readability.
>
> Signed-off-by: Jeff Xu <jeffxu@chromium.org>
Please reply to the points I raised:
https://lore.kernel.org/all/uwwg47m4mwo3g32qavzr2mjmh4r6lcm3irr3wtlvedlylbq74z@flcq2kwvmh46/
They're actually instrumental and something that *needs* to be written down.
--
Pedro
next prev parent reply other threads:[~2024-10-08 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 4:09 [PATCH v3 0/1] " 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
2024-10-08 17:48 ` Pedro Falcato [this message]
2024-10-15 20:00 ` [PATCH v3 1/1] mseal: update mseal.rst 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=CAKbZUD1uyzhS6C0T_F_U+4gfuOcHFMJ-82XsFaLZQj91F-BKZw@mail.gmail.com \
--to=pedro.falcato@gmail.com \
--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=jeffxu@chromium.org \
--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=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