mm/rmap: fix comment in anon_vma_clone()
authorMa Wupeng <mawupeng1@huawei.com>
Fri, 14 Oct 2022 01:39:31 +0000 (09:39 +0800)
committerAndrew Morton <akpm@linux-foundation.org>
Wed, 9 Nov 2022 01:37:12 +0000 (17:37 -0800)
Commit 2555283eb40d ("mm/rmap: Fix anon_vma->degree ambiguity leading to
double-reuse") use num_children and num_active_vmas to replace the origin
degree to fix anon_vma UAF problem.  Update the comment in anon_vma_clone
to fit this change.

Link: https://lkml.kernel.org/r/20221014013931.1565969-1-mawupeng1@huawei.com
Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/rmap.c

index 2ec925e5fa6a9cdb0e954ac21362a632fa452062..92ed6fe3d038f756f7fd9a3081180cd5aa8a146f 100644 (file)
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -315,8 +315,8 @@ int anon_vma_clone(struct vm_area_struct *dst, struct vm_area_struct *src)
 
  enomem_failure:
        /*
-        * dst->anon_vma is dropped here otherwise its degree can be incorrectly
-        * decremented in unlink_anon_vmas().
+        * dst->anon_vma is dropped here otherwise its num_active_vmas can
+        * be incorrectly decremented in unlink_anon_vmas().
         * We can safely do this because callers of anon_vma_clone() don't care
         * about dst->anon_vma if anon_vma_clone() failed.
         */