[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ab5f8765-9300-4781-8076-3035ad41e4af@lucifer.local>
Date: Fri, 29 Nov 2024 11:36:49 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Jann Horn <jannh@...gle.com>,
Shuah Khan <shuah@...nel.org>, Julian Orth <ju.orth@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] mm: reinstate ability to map write-sealed memfd
mappings read-only
On Fri, Nov 29, 2024 at 02:24:33AM -0800, Andrew Morton wrote:
> On Fri, 29 Nov 2024 10:03:51 +0000 Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
>
> > Andrew - This is a hotfix for 6.13, sorry forgot to tag the series as such :)
>
> Jann's feedback didn't sound very ackish?
Obviously Jann can indicate whether he feels this needs work or not, but I
believe we resolved the issues raised?
Mostly concerns around expected behaviour for these operations _in general_
and whether mmap-read'ing memfd write sealed mappings make sense, however
it's by the by, we accidentally regressed user-facing behaviour and so
should restore it.
I also feel I made a case for why it is in fact sane and useful to be able
to mmap memfd-write-sealed mappings :)
But of course - Jann can indicate whether he is happy with this or whether
it needs work, as usual his input is excellent and highly appreciated so
Jann - if you have any remaining concerns - please let me know.
Thanks!
Powered by blists - more mailing lists