Re: [PATCH v2] mm/rmap: synchronize lock and unlock target in anon_vma_clone

On Mon, Aug 17, 2026 at 11:07:49AM +0800, Lance Yang wrote:
>
>
> On 2026/8/17 10:34, Eric Kim wrote:
> > Currently, in anon_vma_clone(), active_anon_vma is assigned from
> > src->anon_vma and is used when unlocking anon_vma after linking
> > new AVCs. However, the corresponding lock operation uses
> > src->anon_vma directly.
> >
> > Use active_anon_vma consistently to make the lock/unlock pair explicit.
> >
> > Signed-off-by: Eric Kim <[email protected]>
> > ---
> > v2:
> > - Clarify the commit message to explain that src->anon_vma and
> >    active_anon_vma refer to the same anon_vma.
>
> Just a heads-up... since only the commit message changed, the Reviewed-by
> tags from v1 still apply, so please carry them over ...

Yup, if you're not fundamentally changing the patch you should retain all
existing tags like this.

FWIW:

Reviewed-by: Lorenzo Stoakes (ARM) <[email protected]>

--
Cheers, Lorenzo