[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230804121416.533bb81336ded8f170da097e@linux-foundation.org>
Date: Fri, 4 Aug 2023 12:14:16 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: torvalds@...ux-foundation.org, jannh@...gle.com,
willy@...radead.org, liam.howlett@...cle.com, david@...hat.com,
peterx@...hat.com, ldufour@...ux.ibm.com, vbabka@...e.cz,
michel@...pinasse.org, jglisse@...gle.com, mhocko@...e.com,
hannes@...xchg.org, dave@...olabs.net, hughd@...gle.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
stable@...r.kernel.org, kernel-team@...roid.com,
Linus Torvalds <torvalds@...uxfoundation.org>
Subject: Re: [PATCH v4 1/6] mm: enable page walking API to lock vmas during
the walk
On Fri, 4 Aug 2023 08:27:19 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:
> walk_page_range() and friends often operate under write-locked mmap_lock.
> With introduction of vma locks, the vmas have to be locked as well
> during such walks to prevent concurrent page faults in these areas.
> Add an additional member to mm_walk_ops to indicate locking requirements
> for the walk.
>
> ...
>
> 18 files changed, 100 insertions(+), 20 deletions(-)
>
That's a big patch for a -stable backport.
Presumably the various -stable maintainers will be wondering why we're
doing this. But, as is so often the case, the changelog fails to
describe any user-visible effects of the change. Please send this info
and I'll add it to the changelog.
Powered by blists - more mailing lists