[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYu-w+3qgkGet4B4NeBxQNaXoWij49j0WRwPAYELgakb6w@mail.gmail.com>
Date: Fri, 15 Nov 2019 14:28:43 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Tejun Heo <tj@...nel.org>
Cc: cgroups@...r.kernel.org,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
namhyung@...nel.org, open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, lizefan@...wei.com,
hannes@...xchg.org, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, kafai@...com,
Song Liu <songliubraving@...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
Hi Tejun,
On Fri, 15 Nov 2019 at 04:12, Tejun Heo <tj@...nel.org> 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
mkdir -p /tmp/cgroup2
mount -t cgroup2 none /tmp/cgroup2
ls -lid /tmp/cgroup2
1 dr-xr-xr-x 5 root root 0 Nov 15 08:00 /tmp/cgroup2
Full test log link,
https://lkft.validation.linaro.org/scheduler/job/1011451#L1170
- Naresh
Powered by blists - more mailing lists