From: Andrew Morton <akpm@linux-foundation.org>
To: jeffxu@chromium.org
Cc: keescook@chromium.org, corbet@lwn.net, jeffxu@google.com,
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,
rdunlap@infradead.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, enh@google.com
Subject: Re: [PATCH v1 1/1] mseal: update mseal.rst
Date: Fri, 27 Sep 2024 12:58:53 -0700 [thread overview]
Message-ID: <20240927125853.60978e0697a317e7965a8d9c@linux-foundation.org> (raw)
In-Reply-To: <20240927185211.729207-2-jeffxu@chromium.org>
On Fri, 27 Sep 2024 18:52:09 +0000 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.
Fixes:what?
I think 4a2dd02b0916 ("mm/mprotect: replace can_modify_mm with
can_modify_vma")?
next prev parent reply other threads:[~2024-09-27 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 18:52 [PATCH v1 0/1] " jeffxu
2024-09-27 18:52 ` [PATCH v1 1/1] mseal: " jeffxu
2024-09-27 19:58 ` Andrew Morton [this message]
2024-09-27 20:04 ` Jeff Xu
2024-09-27 22:59 ` Pedro Falcato
2024-09-28 1:29 ` Jeff Xu
2024-09-28 13:43 ` Pedro Falcato
2024-10-01 0:24 ` Jeff Xu
2024-10-04 17:02 ` Pedro Falcato
2024-10-14 4:49 ` Jeff Xu
2024-09-28 18:28 ` Randy Dunlap
2024-10-01 0:10 ` 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=20240927125853.60978e0697a317e7965a8d9c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--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=jeffxu@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