From: Qi Zheng <qi.zheng@linux.dev>
To: Peiyang He <peiyang_he@smail.nju.edu.cn>,
akpm@linux-foundation.org, david@kernel.org, kasong@tencent.com,
shakeel.butt@linux.dev, baohua@kernel.org,
axelrasmussen@google.com, yuanchu@google.com, weixugc@google.com,
hannes@cmpxchg.org, harry@kernel.org, muchun.song@linux.dev,
mhocko@kernel.org, roman.gushchin@linux.dev, ljs@kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Qi Zheng <zhengqi.arch@bytedance.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] mm: mglru: fix stale batch updates after memcg reparenting
Date: Fri, 26 Jun 2026 12:50:33 +0800 [thread overview]
Message-ID: <46eb172e-7b31-48cc-bfd5-ca4777bf37ef@linux.dev> (raw)
In-Reply-To: <0559695533E1C70F+31684237-e405-48da-ad8f-4ba7ff4ddb38@smail.nju.edu.cn>
Hi Peiyang,
On 6/26/26 12:29 PM, Peiyang He wrote:
> Hi Qi,
>
> I have applied this patch and tested it against the PoC, the warning is not observed anymore in the kernel log.
> Thanks for your nice work!
Thanks a ton for testing this!
>
> Best,
> Peiyang
>
next prev parent reply other threads:[~2026-06-26 4:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:15 [PATCH v3] mm: mglru: fix stale batch updates after memcg reparenting Qi Zheng
2026-06-25 18:41 ` Johannes Weiner
2026-06-26 2:27 ` Qi Zheng
2026-06-26 4:43 ` Harry Yoo
2026-06-26 4:48 ` Qi Zheng
2026-06-26 4:59 ` Harry Yoo
2026-06-26 6:24 ` Qi Zheng
2026-06-26 6:48 ` Harry Yoo
2026-06-26 7:04 ` Qi Zheng
2026-06-26 7:09 ` Harry Yoo
2026-06-26 9:39 ` Johannes Weiner
2026-06-26 11:21 ` Qi Zheng
2026-06-26 17:08 ` Shakeel Butt
2026-06-25 20:22 ` Shakeel Butt
2026-06-26 2:39 ` Qi Zheng
2026-06-26 4:29 ` Peiyang He
2026-06-26 4:50 ` Qi Zheng [this message]
2026-06-26 7:15 ` Harry Yoo
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=46eb172e-7b31-48cc-bfd5-ca4777bf37ef@linux.dev \
--to=qi.zheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=kasong@tencent.com \
--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=peiyang_he@smail.nju.edu.cn \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.