[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240927125853.60978e0697a317e7965a8d9c@linux-foundation.org>
Date: Fri, 27 Sep 2024 12:58:53 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: jeffxu@...omium.org
Cc: keescook@...omium.org, corbet@....net, jeffxu@...gle.com,
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
Subject: Re: [PATCH v1 1/1] mseal: update mseal.rst
On Fri, 27 Sep 2024 18:52:09 +0000 jeffxu@...omium.org wrote:
> From: Jeff Xu <jeffxu@...omium.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")?
Powered by blists - more mailing lists