public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: cgroups@vger.kernel.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	namhyung@kernel.org, open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org, lizefan@huawei.com,
	hannes@cmpxchg.org, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	kafai@fb.com, Song Liu <songliubraving@fb.com>
Subject: Re: linux-next: arm32: beagleboard x15: WARNING: CPU: 0 PID: 0 at /usr/src/kernel/kernel/cgroup/cgroup.c:1969 cgroup_setup_root+0x36c/0x4e8
Date: Thu, 14 Nov 2019 14:42:13 -0800	[thread overview]
Message-ID: <20191114224213.GN4163745@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <CA+G9fYviReoG+gq=Jm8yQOMd01j2opae5p+VTGGMK7aLn0xWgw@mail.gmail.com>

Hello, Naresh.

On Thu, Nov 14, 2019 at 11:02:53AM +0530, Naresh Kamboju wrote:
> [    0.015402] WARNING: CPU: 0 PID: 0 at /usr/src/kernel/kernel/cgroup/cgroup.c:1969
> cgroup_setup_root+0x36c/0x4e8
...
> [    0.015726] [<c053ac48>] (cgroup_setup_root) from [<c1c2a260>]
> (cgroup_init+0x108/0x560)

So, that's saying that the initial kernfs_node ino allocation returned
something other than 1.  Hmmm... x86_32 works fine.  What does the
following say?

# mkdir -p /tmp/cgroup2
# mount -t cgroup2 none /tmp/cgroup2
# ls -lid /tmp/cgroup2

Thanks.

-- 
tejun

  reply	other threads:[~2019-11-14 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  5:32 linux-next: arm32: beagleboard x15: WARNING: CPU: 0 PID: 0 at /usr/src/kernel/kernel/cgroup/cgroup.c:1969 cgroup_setup_root+0x36c/0x4e8 Naresh Kamboju
2019-11-14 22:42 ` Tejun Heo [this message]
2019-11-14 22:54   ` [PATCH cgroup/for-5.5] cgroup: fix incorrect WARN_ON_ONCE() in cgroup_setup_root() Tejun Heo
2019-11-15  8:58   ` linux-next: arm32: beagleboard x15: WARNING: CPU: 0 PID: 0 at /usr/src/kernel/kernel/cgroup/cgroup.c:1969 cgroup_setup_root+0x36c/0x4e8 Naresh Kamboju

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=20191114224213.GN4163745@devbig004.ftw2.facebook.com \
    --to=tj@kernel.org \
    --cc=ast@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=hannes@cmpxchg.org \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=lkft-triage@lists.linaro.org \
    --cc=namhyung@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=songliubraving@fb.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