[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <061bfccf-6828-424c-8fca-2498c48c97e7@suse.cz>
Date: Thu, 10 Jul 2025 16:36:42 +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 06/10] mm/mremap: check remap conditions earlier
On 7/7/25 07:27, Lorenzo Stoakes wrote:
> When we expand or move a VMA, this requires a number of additional checks
> to be performed.
>
> Make it really obvious under what circumstances these checks must be
> performed and aggregate all the checks in one place by invoking this in
> check_prep_vma().
>
> We have to adjust the checks to account for shrink + move operations by
> checking new_len <= old_len rather than new_len == old_len.
>
> No functional change intended.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Reviewed-by: Vlastimil Babka <vbabka@...e.cz>
Powered by blists - more mailing lists