Re: [PATCH v3] mm/rmap: synchronize lock and unlock target in anon_vma_clone
Barry Song <[email protected]>
| Newsgroups | gmane.linux.kernel,gmane.linux.kernel.mm |
|---|---|
| Message-ID | <CAGsJ_4wZkwOVJnsatMXWLnLA56rT5tOgrp9HczaFDHNA6N971g@mail.gmail.com> |
On Mon, Aug 17, 2026 at 11:58 AM Eric Kim <[email protected]> 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. Thanks! Could we add something along these lines? Although they are actually the same thing, use active_anon_vma consistently to make the lock/unlock pair explicit. > > Signed-off-by: Eric Kim <[email protected]> > Reviewed-by: Lorenzo Stoakes (ARM) <[email protected]> > Reviewed-by: Lance Yang <[email protected]> > Reviewed-by: Rik van Riel <[email protected]> > --- With that, Reviewed-by: Barry Song <[email protected]>