From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: liliguang <liliguang@baidu.com>,
cgroups@vger.kernel.org, mhocko@kernel.org,
roman.gushchin@linux.dev, shakeelb@google.com,
songmuchun@bytedance.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm: correctly charge compressed memory to its memcg
Date: Wed, 17 Aug 2022 10:17:01 -0700 [thread overview]
Message-ID: <20220817101701.149fff9ef57f447dd8bb0dc9@linux-foundation.org> (raw)
In-Reply-To: <YvpkK8fwCEPGmif+@cmpxchg.org>
On Mon, 15 Aug 2022 11:20:11 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
> Great catch. I think this qualifies for stable.
>
> Cc: stable@vger.kernel.org # 5.19
> Fixes: f4840ccfca25 ("zswap: memcg accounting")
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>
> Andrew, can you please take this through the MM tree?
Sure, but I'm not subscribed to cgroups@ and it wasn't cc'ed to
linux-kernel so no patch for me.
I could reconstitute it from the quoted patch but that's a bit lame and
we don't get a usable Link: tag.
So please redo, refresh, retest and resend?
next prev parent reply other threads:[~2022-08-17 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220811081913.102770-1-liliguang@baidu.com>
[not found] ` <YvWa9MOQWBICInjO@P9FQF9L96D.corp.robot.car>
2022-08-12 21:56 ` Shakeel Butt
2022-08-13 0:43 ` Yosry Ahmed
2022-08-15 2:52 ` Li,Liguang
2022-08-15 8:09 ` Yosry Ahmed
2022-08-15 11:48 ` Li,Liguang
2022-08-15 13:46 ` Yosry Ahmed
2022-08-15 15:31 ` Johannes Weiner
2022-08-15 15:42 ` Yosry Ahmed
2022-08-15 16:16 ` Yosry Ahmed
2022-08-15 17:47 ` Johannes Weiner
2022-08-15 17:55 ` Yosry Ahmed
2022-08-16 22:19 ` Shakeel Butt
2022-08-15 6:52 ` Muchun Song
2022-08-15 15:20 ` Johannes Weiner
2022-08-17 17:17 ` Andrew Morton [this message]
2022-11-14 19:48 Johannes Weiner
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=20220817101701.149fff9ef57f447dd8bb0dc9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=liliguang@baidu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox