From: create0818@163.com
To: Vlastimil Babka (SUSE) <vbabka@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Liam R. Howlett <Liam.Howlett@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
syzbot+1a3353a77896e73a8f53@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/memcontrol: restore irq wrapper for lruvec_stat_mod_folio()
Date: Thu, 16 Apr 2026 00:22:53 +0800 [thread overview]
Message-ID: <177627017370.51713.13753959033860067852@163.com> (raw)
In-Reply-To: <ef2d8f65-b3b4-4a9c-a77f-78ad1cadff28@kernel.org>
Hi,
Sorry for the noise and for sending an insufficiently validated conclusion earlier. I rechecked this more carefully, and my earlier conclusion was not well founded.
I can no longer justify
memcg_validate_race: fixed start/end mismatch (1 -> 0)
as evidence for this patch.
I rebuilt an apples-to-apples baseline/fixed pair from the same source base and reran the QEMU validation. The result is:
- baseline and fixed both reproduce the warning under the original remount-based harness
- baseline and fixed both stop reproducing it under a no-remount harness
- the validation workers still start in the no-remount case
So this warning does not distinguish the wrapper patch from baseline behavior. At this point it appears to be induced by the remount/rebind test harness itself, not evidence of a wrapper-specific regression.
I do not have a reproducer that distinguishes baseline from the patched kernel, so I am dropping this patch from this line of argument.
Assisted-by: OpenAI Codex: GPT-5.4 [shell] [qemu]
prev parent reply other threads:[~2026-04-15 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:48 Cao Ruichuang
2026-04-13 16:44 ` Shakeel Butt
2026-04-14 7:56 ` Vlastimil Babka (SUSE)
2026-04-15 16:22 ` create0818 [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=177627017370.51713.13753959033860067852@163.com \
--to=create0818@163.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=syzbot+1a3353a77896e73a8f53@syzkaller.appspotmail.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