From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Shawn Bohrer <shawn.bohrer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: 3.10.16 cgroup css_set_lock deadlock
Date: Fri, 15 Nov 2013 17:19:29 +0900 [thread overview]
Message-ID: <20131115081929.GA11530@mtj.dyndns.org> (raw)
In-Reply-To: <20131114232529.GB16725-/vebjAlq/uFE7V8Yqttd03bhEEblAqRIDbRjUBewulXQT0dZR+AlfA@public.gmane.org>
On Thu, Nov 14, 2013 at 05:25:29PM -0600, Shawn Bohrer wrote:
> In trying to reproduce the cgroup_mutex deadlock I reported earlier
> in https://lkml.org/lkml/2013/11/11/574 I believe I encountered a
> different issue that I'm also unable to understand. This machine
> started out reporting some soft lockups that look to me like they are
> on a read_lock(css_set_lock):
>
...
> RIP: 0010:[<ffffffff8109253c>] [<ffffffff8109253c>] cgroup_attach_task+0xdc/0x7a0
...
> [<ffffffff81092e87>] attach_task_by_pid+0x167/0x1a0
> [<ffffffff81092ef3>] cgroup_tasks_write+0x13/0x20
Most likely the bug fixed by ea84753c98a7 ("cgroup: fix to break the
while loop in cgroup_attach_task() correctly"). 3.10.19 contains the
backported fix.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-11-15 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 23:25 3.10.16 cgroup css_set_lock deadlock Shawn Bohrer
[not found] ` <20131114232529.GB16725-/vebjAlq/uFE7V8Yqttd03bhEEblAqRIDbRjUBewulXQT0dZR+AlfA@public.gmane.org>
2013-11-15 8:19 ` Tejun Heo [this message]
[not found] ` <20131115081929.GA11530-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-11-15 14:53 ` Don Morris
[not found] ` <5286355A.9060509-VXdhtT5mjnY@public.gmane.org>
2013-11-16 5:18 ` Tejun Heo
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=20131115081929.GA11530@mtj.dyndns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=shawn.bohrer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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