[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8074f0b2-c4c0-46ac-aca8-a395f30ab61d@suse.cz>
Date: Thu, 10 Jul 2025 16:47:23 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Peter Xu <peterx@...hat.com>, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>, Jann Horn <jannh@...gle.com>,
Pedro Falcato <pfalcato@...e.de>, Rik van Riel <riel@...riel.com>,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 08/10] mm/mremap: clean up mlock populate behaviour
On 7/7/25 07:27, Lorenzo Stoakes wrote:
> When an mlock()'d VMA is expanded, we need to populate the expanded region
> to maintain the contract that all mlock()'d memory is present (albeit -
> with some period after mmap unlock where the expanded part of the mapping
> remains unfaulted).
>
> The current implementation is very unclear, so make it absolutely explicit
> under what circumstances we do this.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Reviewed-by: Vlastimil Babka <vbabka@...e.cz>
Powered by blists - more mailing lists