From: Suren Baghdasaryan <surenb@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Peter Xu <peterx@redhat.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Lokesh Gidra <lokeshgidra@google.com>,
Alistair Popple <apopple@nvidia.com>
Subject: Re: [PATCH] mm: Always sanity check anon_vma first for per-vma locks
Date: Fri, 12 Apr 2024 09:53:29 -0500 [thread overview]
Message-ID: <CAJuCfpGGUD6ev-KFhON2D2RqQRZSgjxFXvkNqeux-LrJw4L+iw@mail.gmail.com> (raw)
In-Reply-To: <ZhlCVOz7qaDtldfL@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
On Fri, Apr 12, 2024, 9:16 AM Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Apr 12, 2024 at 06:06:46AM -0700, Suren Baghdasaryan wrote:
> > > On Fri, Apr 12, 2024 at 04:14:16AM +0100, Matthew Wilcox wrote:
> > > > - /*
> > > > - * find_mergeable_anon_vma uses adjacent vmas which are not
> locked.
> > > > - * This check must happen after vma_start_read(); otherwise,
> a
> > > > - * concurrent mremap() with MREMAP_DONTUNMAP could
> dissociate the VMA
> > > > - * from its anon_vma.
> > > > - */
> > > > - if (unlikely(vma_is_anonymous(vma) && !vma->anon_vma))
> > > > - goto inval_end_read;
> > > > -
> > > > /* Check since vm_start/vm_end might change before we lock
> the VMA */
> > > > if (unlikely(address < vma->vm_start || address >=
> vma->vm_end))
> > > > goto inval_end_read;
> > > >
> > > > That takes a few insns out of the page fault path (good!) at the cost
> > > > of one extra trip around the fault handler for the first fault on an
> > > > anon vma. It makes the file & anon paths more similar to each other
> > > > (good!)
> > > >
> > > > We'd need some data to be sure it's really a win, but less code is
> > > > always good.
> >
> > I agree, if we make this change we should keep this comment and maybe
> > move it into vmf_anon_prepare()
>
> Most of the comment makes no sense if you move it out of
> lock_vma_under_rcu(). It's justifying where it needs to be in that
> function. If it's no longer in that function, there's not much left of
> the comment. What part do you think is valuable and needs to be retained?
>
Unless vmf_anon_prepare() already explains why vma->anon_vma poses a
problem for per-vma locks, we should have an explanation there. This
comment would serve that purpose IMO.
>
[-- Attachment #2: Type: text/html, Size: 2786 bytes --]
next prev parent reply other threads:[~2024-04-12 14:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 17:06 Peter Xu
2024-04-10 20:26 ` Matthew Wilcox
[not found] ` <Zhb6B8UsidEEbFu3@x1n>
2024-04-10 21:10 ` Matthew Wilcox
2024-04-10 21:23 ` Peter Xu
2024-04-10 23:59 ` Matthew Wilcox
2024-04-11 0:20 ` Peter Xu
2024-04-11 14:50 ` Matthew Wilcox
2024-04-11 15:34 ` Peter Xu
2024-04-11 17:14 ` Matthew Wilcox
2024-04-11 15:42 ` Suren Baghdasaryan
2024-04-11 17:13 ` Liam R. Howlett
[not found] ` <ZhhSItiyLYBEdAX3@x1n>
2024-04-11 21:27 ` Matthew Wilcox
2024-04-11 21:46 ` Peter Xu
2024-04-11 22:02 ` Matthew Wilcox
2024-04-12 3:14 ` Matthew Wilcox
2024-04-12 12:38 ` Peter Xu
2024-04-12 13:06 ` Suren Baghdasaryan
2024-04-12 14:16 ` Matthew Wilcox
2024-04-12 14:53 ` Suren Baghdasaryan [this message]
2024-04-12 15:19 ` Matthew Wilcox
2024-04-12 15:31 ` Matthew Wilcox
2024-04-13 21:46 ` Suren Baghdasaryan
2024-04-13 22:52 ` Matthew Wilcox
2024-04-13 23:11 ` Suren Baghdasaryan
2024-04-13 21:41 ` Suren Baghdasaryan
2024-04-13 22:46 ` Matthew Wilcox
2024-04-15 15:58 ` Suren Baghdasaryan
2024-04-15 16:13 ` Matthew Wilcox
2024-04-15 16:19 ` Suren Baghdasaryan
2024-04-15 16:26 ` Matthew Wilcox
2024-04-12 12:46 ` Suren Baghdasaryan
2024-04-12 13:32 ` Matthew Wilcox
2024-04-12 13:46 ` Suren Baghdasaryan
2024-04-26 14:00 ` Matthew Wilcox
2024-04-26 15:07 ` Suren Baghdasaryan
2024-04-26 15:28 ` Matthew Wilcox
2024-04-26 15:32 ` Suren Baghdasaryan
2024-04-26 15:50 ` Matthew Wilcox
2024-04-26 15:32 ` Liam R. Howlett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJuCfpGGUD6ev-KFhON2D2RqQRZSgjxFXvkNqeux-LrJw4L+iw@mail.gmail.com \
--to=surenb@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=peterx@redhat.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox