From: Andrew Morton <akpm@linux-foundation.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Pedro Falcato <pfalcato@suse.de>,
Suren Baghdasaryan <surenb@google.com>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
David Hildenbrand <david@kernel.org>,
Mike Rapoport <rppt@kernel.org>, Michal Hocko <mhocko@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Jann Horn <jannh@google.com>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
Daehyeon Ko <4ncienth@gmail.com>
Subject: Re: [PATCH v2] mm/vma: avoid spurious write locks when mm->mm_lock_seq overflows
Date: Mon, 19 Oct 2026 07:32:01 -0700 [thread overview]
Message-ID: <20261019073201.aee381fbbdf2edfdd0a68754@linux-foundation.org> (raw)
In-Reply-To: <atYJA7nIu_RwpoCC@gremlin>
On Mon, 19 Oct 2026 13:19:45 +0100 "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:
> On Mon, Oct 19, 2026 at 10:53:27AM +0100, Pedro Falcato wrote:
> > On Fri, Oct 16, 2026 at 12:34:33PM +0100, Lorenzo Stoakes (ARM) wrote:
>
> > > So I think it's fine to just send it (early :) in the merge window.
> > > ---
> > > v2:
> > > * Updated comment in vma_seqcount_is_write_locked() to mention the VMA
> > > being attached.
> > > * Renamed reset_vma_seqcounts() to __mm_reset_vma_seqcounts().
> > > * Used acquire semantics in vma_start_reads() to avoid race with reset -
> > > there is another acquire immediately after this one so it should just be
> > > noise perf-wise.
> > > * Removed stable tag, will do the backports manually (just make the value
> > > 64 bits...)
> >
> > I guess you're fitting this where __vm_anon_pgoff_lo now sits? If so, then
> > this patch probably wants backporting to 7.3.
>
> Ack.
I added cc:stable to the mm.git copy of this.
next prev parent reply other threads:[~2026-10-19 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 11:34 [PATCH v2] mm/vma: avoid spurious write locks when mm->mm_lock_seq overflows Lorenzo Stoakes (ARM)
2026-10-16 12:16 ` Jose A. Perez de Azpillaga
2026-10-16 14:55 ` Lorenzo Stoakes (ARM)
2026-10-17 3:12 ` Andrew Morton
2026-10-19 9:53 ` Pedro Falcato
2026-10-19 12:19 ` Lorenzo Stoakes (ARM)
2026-10-19 14:32 ` Andrew Morton [this message]
2026-10-19 14:39 ` Lorenzo Stoakes (ARM)
2026-10-19 14:40 ` Lorenzo Stoakes (ARM)
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=20261019073201.aee381fbbdf2edfdd0a68754@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=4ncienth@gmail.com \
--cc=azpijr@gmail.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.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