From: Sasha Levin <sashal@kernel.org>
To: lorenzo.stoakes@oracle.com
Cc: akpm@linux-foundation.org, david@kernel.org, gavinguo@igalia.com,
hughd@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, sashal@kernel.org, ziy@nvidia.com
Subject: [WIP] mm/vma: clear dst->anon_vma on anon_vma_clone() failure in dup_anon_vma()
Date: Mon, 2 Mar 2026 10:15:47 -0500 [thread overview]
Message-ID: <20260302151547.2389070-1-sashal@kernel.org> (raw)
In-Reply-To: <9e273ce7-8471-495c-a344-d9bf61cb808c@lucifer.local>
When dup_anon_vma() calls anon_vma_clone() and it fails with -ENOMEM,
dst->anon_vma is left pointing at src->anon_vma without a corresponding
num_active_vmas increment (which only happens on the success path).
The internal cleanup_partial_anon_vmas() correctly frees partially-
allocated AVCs but does not clear dst->anon_vma. Later, when the VMA is
torn down during process exit, unlink_anon_vmas() sees a non-NULL
vma->anon_vma and decrements num_active_vmas without a prior matching
increment, causing an underflow. This eventually triggers:
WARNING: mm/rmap.c:528 at unlink_anon_vmas+0x68e/0x900 mm/rmap.c:528
First, fault injection in the mlock2 syscall path:
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 3 PID: 4261 Comm: syz.6.96
Call Trace:
should_fail_ex.cold+0xd8/0x15d
should_failslab+0xd4/0x150
kmem_cache_alloc_noprof+0x60/0x630
anon_vma_clone+0x2ed/0xcf0
dup_anon_vma+0x1cb/0x320
vma_modify+0x16dd/0x2230
vma_modify_flags+0x1f9/0x350
mlock_fixup+0x225/0xe10
apply_vma_lock_flags+0x249/0x360
do_mlock+0x269/0x7f0
__x64_sys_mlock2+0xc0/0x100
Followed by the WARNING on the same task during exit:
WARNING: mm/rmap.c:528 at unlink_anon_vmas+0x68e/0x900
CPU: 3 PID: 4261 Comm: syz.6.96
Call Trace:
free_pgtables+0x312/0x950
exit_mmap+0x487/0xa80
__mmput+0x11b/0x540
exit_mm
do_exit+0x7b9/0x2c60
Fix this by clearing dst->anon_vma on clone failure, restoring the VMA
to its original unfaulted state. This ensures unlink_anon_vmas() will
correctly bail out early at the !active_anon_vma check.
Other callers of anon_vma_clone() are unaffected: VMA_OP_SPLIT/REMAP
free the dst VMA on error, and VMA_OP_FORK explicitly sets anon_vma to
NULL before cloning.
Fixes: 542eda1a83294 ("mm/rmap: improve anon_vma_clone(), unlink_anon_vmas() comments, add asserts")
Assisted-by: Claude:claude-opus-4-6
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
mm/vma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mm/vma.c b/mm/vma.c
index be64f781a3aa7..4cf6a2a05c10a 100644
--- a/mm/vma.c
+++ b/mm/vma.c
@@ -629,8 +629,10 @@ static int dup_anon_vma(struct vm_area_struct *dst,
vma_assert_write_locked(dst);
dst->anon_vma = src->anon_vma;
ret = anon_vma_clone(dst, src, VMA_OP_MERGE_UNFAULTED);
- if (ret)
+ if (ret) {
+ dst->anon_vma = NULL;
return ret;
+ }
*dup = dst;
}
--
2.51.0
next prev parent reply other threads:[~2026-03-02 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 13:43 VM_BUG_ON_VMA in split_huge_pmd_locked: huge PMD doesn't cover full VMA range Sasha Levin
2026-02-25 13:50 ` David Hildenbrand (Arm)
2026-02-25 18:12 ` Sasha Levin
2026-03-02 10:57 ` Lorenzo Stoakes
2026-03-02 15:13 ` Sasha Levin
2026-03-02 15:15 ` Sasha Levin [this message]
2026-03-02 17:48 ` [WIP] mm/vma: clear dst->anon_vma on anon_vma_clone() failure in dup_anon_vma() Lorenzo Stoakes
2026-02-25 20:30 ` VM_BUG_ON_VMA in split_huge_pmd_locked: huge PMD doesn't cover full VMA range David Hildenbrand (Arm)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260302151547.2389070-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=gavinguo@igalia.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox