On Fri, Oct 13, 2023 at 1:04 AM David Hildenbrand wrote:
>
> On 13.10.23 00:01, Peter Xu wrote:
> > On Sun, Oct 08, 2023 at 11:42:26PM -0700, Suren Baghdasaryan wrote:
> >> From: Andrea Arcangeli
> >>
> >> For now, folio_move_anon_rmap() was only used to move a folio to a
> >> different anon_vma
On 13.10.23 00:01, Peter Xu wrote:
On Sun, Oct 08, 2023 at 11:42:26PM -0700, Suren Baghdasaryan wrote:
From: Andrea Arcangeli
For now, folio_move_anon_rmap() was only used to move a folio to a
different anon_vma after fork(), whereby the root anon_vma stayed
unchanged. For that, it was
On Sun, Oct 08, 2023 at 11:42:26PM -0700, Suren Baghdasaryan wrote:
> From: Andrea Arcangeli
>
> For now, folio_move_anon_rmap() was only used to move a folio to a
> different anon_vma after fork(), whereby the root anon_vma stayed
> unchanged. For that, it was sufficient to hold the folio lock
From: Andrea Arcangeli
For now, folio_move_anon_rmap() was only used to move a folio to a
different anon_vma after fork(), whereby the root anon_vma stayed
unchanged. For that, it was sufficient to hold the folio lock when
calling folio_move_anon_rmap().
However, we want to make use of
