From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.com>, Tao Cui <cui.tao@linux.dev>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, hannes@cmpxchg.org,
roman.gushchin@linux.dev, muchun.song@linux.dev,
Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH] mm: page_counter: reject empty string in page_counter_memparse()
Date: Sat, 29 Aug 2026 17:53:14 -0700 [thread overview]
Message-ID: <apN-zc_5SIEkdzB6@linux.dev> (raw)
In-Reply-To: <20260829174220.204771edba7c52511dc08641@linux-foundation.org>
On Sat, Aug 29, 2026 at 05:42:20PM -0700, Andrew Morton wrote:
> On Wed, 19 Aug 2026 09:00:36 +0200 Michal Hocko <mhocko@suse.com> wrote:
>
> > > Whether that benefit outweighs the compatibility risk is not mine to
> > > decide.
> >
> > And I am still not convinced. I do understand your frustration from the
> > debugging the issue. In any way, if other maintainers decide this change
> > is worth I will not stand in the way.
>
> Shakeel seems OK with it. Other other maintainers are being aloof ;)
>
> I'll queue it for now, along with a note that additional poking is
> needed.
>
> A v2 would be nice, please. Add details about that production incident
> and make the requested update to
> Documentation/admin-guide/cgroup-v2.rst.
V2 is already out and we decided to make it a documented behavior.
https://lore.kernel.org/20260826021753.197871-1-cui.tao@linux.dev
prev parent reply other threads:[~2026-08-30 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 4:26 [PATCH] mm: page_counter: reject empty string in page_counter_memparse() Tao Cui
2026-08-17 16:16 ` Shakeel Butt
2026-08-18 7:45 ` Michal Hocko
2026-08-18 15:06 ` Shakeel Butt
2026-08-18 16:43 ` Michal Hocko
2026-08-19 3:00 ` Tao Cui
2026-08-19 7:00 ` Michal Hocko
2026-08-30 0:42 ` Andrew Morton
2026-08-30 0:53 ` Shakeel Butt [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=apN-zc_5SIEkdzB6@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
/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.