From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Jiakai Xu <jiakaipeanut@gmail.com>
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
david@kernel.org, harry.yoo@oracle.com, jannh@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@surriel.com, sashal@kernel.org, vbabka@kernel.org
Subject: Re: [BUG] WARNING in unlink_anon_vmas()
Date: Thu, 19 Mar 2026 10:53:43 +0000 [thread overview]
Message-ID: <999476e7-6a68-453f-95ca-7badae20b617@lucifer.local> (raw)
In-Reply-To: <20260319011633.1874-1-jiakaiPeanut@gmail.com>
On Thu, Mar 19, 2026 at 09:16:33AM +0800, Jiakai Xu wrote:
> > Fix at
> > https://lore.kernel.org/linux-mm/20260318122632.63404-1-ljs@kernel.org/
>
> Thank you for the quick investigation and fix.
>
> >
> > We like to turn things around quick in mm ;)
> >
> > Could you check to make sure that fixes the issue? If so could you reply to
> > that email with:
> >
> > Tested-by: Jiakai Xu <jiakaipeanut@gmail.com>
>
> I tested the patch on my setup with the reproducer that originally
> triggered the WARNING in unlink_anon_vmas(), and the issue no longer
> reproduces.
Perfect, much appreciated! :)
Thanks again for submitting the bug, it's been very helpful in ensuring this
issue is addressed in an -rc rather than in a released kernel.
>
> Best regards,
> Jiakai
Thanks, Lorenzo
prev parent reply other threads:[~2026-03-19 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:42 Jiakai Xu
2026-03-18 10:57 ` David Hildenbrand (Arm)
2026-03-18 11:05 ` Lorenzo Stoakes (Oracle)
2026-03-18 10:59 ` Lorenzo Stoakes (Oracle)
2026-03-18 11:23 ` Lorenzo Stoakes (Oracle)
2026-03-18 11:41 ` Lorenzo Stoakes (Oracle)
2026-03-18 11:55 ` Lorenzo Stoakes (Oracle)
2026-03-18 12:28 ` Lorenzo Stoakes (Oracle)
2026-03-19 1:16 ` Jiakai Xu
2026-03-19 10:53 ` Lorenzo Stoakes (Oracle) [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=999476e7-6a68-453f-95ca-7badae20b617@lucifer.local \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=jiakaipeanut@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=sashal@kernel.org \
--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