From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Roman Gushchin <guro@fb.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Cgroups <cgroups@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Michal Hocko <mhocko@kernel.org>,
Shakeel Butt <shakeelb@google.com>,
Kernel Team <kernel-team@fb.com>,
lkft-triage@lists.linaro.org
Subject: Re: [PATCH v3 4/5] mm: memcg: charge memcg percpu memory to the parent cgroup
Date: Fri, 14 Aug 2020 09:27:02 +1000 [thread overview]
Message-ID: <20200814092702.137f588e@canb.auug.org.au> (raw)
In-Reply-To: <CA+G9fYuTsjEpDpODGcYf5hnGwzxj__tVdCMpWeC+ojg5pkYCzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Hi Naresh,
On Thu, 13 Aug 2020 14:46:51 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> The kernel warnings were noticed on linux next 20200813 while booting
> on arm64, arm, x86_64 and i386.
>
> metadata:
> git branch: master
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git commit: e6d113aca646fb6a92b237340109237fd7a9c770
> git describe: next-20200813
> make_kernelversion: 5.8.0
> kernel-config:
> https://builds.tuxbuild.com/YQHc_PpEV-DF8rU7N9tlIQ/kernel.config
Actually in Linus' tree.
It has been fixed today. Thanks for reporting.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-08-13 23:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200623184515.4132564-1-guro@fb.com>
[not found] ` <20200623184515.4132564-2-guro@fb.com>
2020-06-24 0:58 ` [PATCH v3 1/5] percpu: return number of released bytes from pcpu_free_area() Shakeel Butt
[not found] ` <20200623184515.4132564-3-guro@fb.com>
2020-06-24 1:25 ` [PATCH v3 2/5] mm: memcg/percpu: account percpu memory to memory cgroups Shakeel Butt
[not found] ` <20200623184515.4132564-4-guro@fb.com>
2020-06-24 1:35 ` [PATCH v3 3/5] mm: memcg/percpu: per-memcg percpu memory statistics Shakeel Butt
2020-08-11 15:05 ` Johannes Weiner
[not found] ` <20200623184515.4132564-5-guro@fb.com>
2020-06-24 1:40 ` [PATCH v3 4/5] mm: memcg: charge memcg percpu memory to the parent cgroup Shakeel Butt
2020-06-24 1:49 ` Roman Gushchin
2020-07-29 17:10 ` Michal Koutný
2020-08-07 4:16 ` Andrew Morton
2020-08-07 4:37 ` Roman Gushchin
2020-08-10 19:33 ` Roman Gushchin
2020-08-11 14:47 ` Michal Koutný
2020-08-11 16:55 ` Roman Gushchin
2020-08-11 18:32 ` Michal Koutný
2020-08-11 19:32 ` Roman Gushchin
2020-08-12 16:28 ` Michal Koutný
2020-08-11 15:27 ` Johannes Weiner
2020-08-11 17:06 ` Roman Gushchin
2020-08-13 9:16 ` Naresh Kamboju
2020-08-13 23:27 ` Stephen Rothwell [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=20200814092702.137f588e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhocko@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=shakeelb@google.com \
--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;
as well as URLs for NNTP newsgroup(s).