Thread (48 messages) 48 messages, 5 authors, 2026-04-13

Re: [PATCH v4 07/21] mm: have mmap_action_complete() handle the rmap lock and unmap

From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Date: 2026-03-24 14:38:11
Also in: linux-doc, linux-fsdevel, linux-hyperv, linux-mm, linux-scsi, linux-staging, lkml, target-devel

On 3/20/26 23:39, Lorenzo Stoakes (Oracle) wrote:
Rather than have the callers handle this both the rmap lock release and
unmapping the VMA on error, handle it within the mmap_action_complete()
logic where it makes sense to, being careful not to unlock twice.

This simplifies the logic and makes it harder to make mistake with this,
while retaining correct behaviour with regard to avoiding deadlocks.

Also replace the call_action_complete() function with a direct invocation
of mmap_action_complete() as the abstraction is no longer required.

Also update the VMA tests to reflect this change.

Signed-off-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
Nice simplification.

Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help