Hi Andrew, Could you apply the below fix-patch to resolve the issue Chris's AI checks detected, I missed out one caller of mlock_future_ok() (a very human mistake ;)).
Cheers, Lorenzo ----8<---- >From 652146b4d93a31bb6f9da9428ddaab8a4a53e170 Mon Sep 17 00:00:00 2001 From: Lorenzo Stoakes <[email protected]> Date: Wed, 28 Jan 2026 16:41:55 +0000 Subject: [PATCH] fix Signed-off-by: Lorenzo Stoakes <[email protected]> --- mm/mmap.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mm/mmap.c b/mm/mmap.c index 354479c95896..5dfe57b6d69a 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -108,7 +108,8 @@ static int check_brk_limits(unsigned long addr, unsigned long len) if (IS_ERR_VALUE(mapped_addr)) return mapped_addr; - return mlock_future_ok(current->mm, current->mm->def_flags, len) + return mlock_future_ok(current->mm, + current->mm->def_flags & VM_LOCKED, len) ? 0 : -EAGAIN; } -- 2.52.0
