From: Tejun Heo <tj@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Li Zefan <lizefan@huawei.com>,
cgroups@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [BUG] cgroup lockup while upgrading udev on debian
Date: Mon, 22 Jan 2018 08:30:51 -0800 [thread overview]
Message-ID: <20180122163051.GE1096857@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180121213108.4218693b@gandalf.local.home>
Hello, Steven.
On Sun, Jan 21, 2018 at 09:31:08PM -0500, Steven Rostedt wrote:
> While upgrading my system, it locked up while upgrading udev. It locked
> up on vanilla v4.14.12, and it also locked up on debian's 4.14 kernel
> as well. When I booted debian's 4.9 kernel, it upgraded fine.
>
> Note, this is my main server and not a development box. It is not
> something I'm going to run bisects or other tests on. I don't even have
> it logging to serial console (hence the photo). It's serials are hooked
> to my test boxes. That is, it receives logs, it's not set up to send
> them.
>
> Attached in the photo of the crash that happened when I did:
>
> # dpkg --configure udev
It looks like the same bug which was fixed by 74d0833c659a ("cgroup:
fix css_task_iter crash on CSS_TASK_ITER_PROC"). The bug got
introduced durinv v4.14 cycle and triggers when cgroup1 and cgroup2
are used at the same time, which the recent versions of systemd does
when in cgroup1 mode.
Thanks.
--
tejun
next parent reply other threads:[~2018-01-22 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180121213108.4218693b@gandalf.local.home>
2018-01-22 16:30 ` Tejun Heo [this message]
2018-01-22 16:41 ` [BUG] cgroup lockup while upgrading udev on debian Steven Rostedt
[not found] ` <20180122163051.GE1096857-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-22 16:46 ` Greg Kroah-Hartman
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=20180122163051.GE1096857@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rostedt@goodmis.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