From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: SJ Park <sj@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
gregkh@linuxfoundation.org, 4ncienth@gmail.com,
akpm@linux-foundation.org, azpijr@gmail.com, corbet@lwn.net,
david@kernel.org, jannh@google.com, liam@infradead.org,
mhocko@suse.com, patches@lists.linux.dev, pfalcato@suse.de,
rdunlap@infradead.org, rppt@kernel.org, shakeel.butt@linux.dev,
stable@vger.kernel.org, surenb@google.com, vbabka@kernel.org,
linux-mm@kvack.org, Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH 7.3 463/507] mm/vma: avoid spurious write locks when mm->mm_lock_seq overflows
Date: Sat, 14 Nov 2026 17:45:25 +0000 [thread overview]
Message-ID: <avieGNg0Z0WsD17N@gremlin> (raw)
In-Reply-To: <20261114154112.3718615-1-sashal@kernel.org>
On Sat, Nov 14, 2026 at 10:41:11AM -0500, Sasha Levin wrote:
> On Fri, Nov 13, 2026 at 07:19:42PM -0800, SJ Park wrote:
> > On Sat, 14 Nov 2026 01:39:12 +0100 Miguel Ojeda <ojeda@kernel.org> wrote:
> >> ./include/linux/mmap_lock.h:604:20: error: no member named 'mm_lock_seq' in 'struct mm_struct'
> >
> > I found same thing while running kunit. I also confirmed both applying commit
> > 47e725702b0b from Dave and reverting this patch fix the problem on my setup.
>
> Dropped from the 7.3 queue, together with the prerequisite it pulled in.
>
> Thanks to both of you for the report and the confirmation.
I'll send a fixup.
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-11-14 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261113153812.408825269@linuxfoundation.org>
2026-11-14 0:39 ` [PATCH 7.3 463/507] mm/vma: avoid spurious write locks when mm->mm_lock_seq overflows Miguel Ojeda
2026-11-14 3:19 ` SJ Park
2026-11-14 15:41 ` Sasha Levin
2026-11-14 17:45 ` Lorenzo Stoakes (ARM) [this message]
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=avieGNg0Z0WsD17N@gremlin \
--to=ljs@kernel.org \
--cc=4ncienth@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=azpijr@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=pfalcato@suse.de \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--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