From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
"Liam R . Howlett" <liam@infradead.org>,
David Hildenbrand <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>, Jann Horn <jannh@google.com>,
Michal Hocko <mhocko@suse.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: prevent VMA generation reuse from skipping readers
Date: Thu, 15 Oct 2026 17:28:00 +0100 [thread overview]
Message-ID: <atD8jesRoc38xF0J@gremlin> (raw)
In-Reply-To: <20261015143735.1630957-1-4ncienth@gmail.com>
NAK.
You're making VMAs a cache line bigger.
Since this is the second time you've done this - stop sending patches to mm, we
don't want your AI slop, thanks.
(In future you'll likely be ignored.)
On Thu, Oct 15, 2026 at 11:37:35PM +0900, Daehyeon Ko wrote:
> Both values are 32-bit. After 2^31 complete mmap write-lock acquisitions,
> an old VMA stamp can alias the live odd generation. vma_start_write() then
> returns without waiting for an existing reader.
This is really unclear, I guess, as before, a member of the core team (likely
me) will assess this to see if there's anything actually valid here.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-15 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:37 [PATCH] mm: prevent VMA generation reuse from skipping readers Daehyeon Ko
2026-10-15 16:28 ` Lorenzo Stoakes (ARM) [this message]
2026-10-15 18:13 ` 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=atD8jesRoc38xF0J@gremlin \
--to=ljs@kernel.org \
--cc=4ncienth@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--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