From: Andrew Morton <akpm@linux-foundation.org>
To: Ridong Chen <ridong.chen@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
David Finkel <davidf@vimeo.com>, Tejun Heo <tj@kernel.org>,
"open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
<cgroups@vger.kernel.org>,
"open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)"
<linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Tao Cui <cuitao@kylinos.cn>,
Ridong Chen <chenridong@xiaomi.com>
Subject: Re: [PATCH v4 0/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark
Date: Thu, 20 Aug 2026 15:55:56 -0700 [thread overview]
Message-ID: <20260820155556.8e95067fe0402cd83ed48dab@linux-foundation.org> (raw)
In-Reply-To: <ee4cd3ab-0708-4c37-b597-703a7d7547e2@linux.dev>
On Thu, 20 Aug 2026 16:43:23 +0800 Ridong Chen <ridong.chen@linux.dev> wrote:
>
>
> >
> > Ridong Chen (2):
> > memcg: acquire peaks_lock when reading memory.peak
> > mm, memcg: fix memory.peak reset clobbering other fds' watermark
> >
> > mm/memcontrol.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
>
> Hi all,
>
> Just a quick reminder on this series, could it be applied?
> Sending this note in case it got buried.
New material doesn't get a lot of attention during late -rc and during
the merge window. I've set this series aside for consideration late in the
merge window, but a resend at that time (or shortly after -rc1) would
be helpful.
prev parent reply other threads:[~2026-08-20 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 3:30 [PATCH v4 0/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark Ridong Chen
2026-08-14 3:30 ` [PATCH v4 1/2] memcg: acquire peaks_lock when reading memory.peak Ridong Chen
2026-08-14 3:42 ` Muchun Song
[not found] ` <20260814033005.2481920-3-ridong.chen@linux.dev>
2026-08-15 0:38 ` [PATCH v4 2/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark Shakeel Butt
2026-08-20 8:43 ` [PATCH v4 0/2] " Ridong Chen
2026-08-20 22:55 ` Andrew Morton [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=20260820155556.8e95067fe0402cd83ed48dab@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=cuitao@kylinos.cn \
--cc=davidf@vimeo.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=ridong.chen@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@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