From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Tommi Rantala
<tt.rantala-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: cgroup_release_agent() hung task warnings
Date: Tue, 05 Mar 2013 12:28:04 +1100 [thread overview]
Message-ID: <87d2ved49n.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130304173358.GB30413-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> writes:
> (cc'ing Rusty Russell)
>
> On Mon, Mar 04, 2013 at 10:59:58AM +0800, Li Zefan wrote:
>> On 2013/3/3 3:23, Tommi Rantala wrote:
>> > Hello,
>> >
>> > I'm seeing the following hung task warnings when fuzzing the kernel
>> > with trinity (in a qemu virtual machine, as the root user), that I
>> > have not seen before with 3.8 or earlier. The kernel is
>> > b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50 (Merge tag
>> > 'lzo-update-signature-20130226' of
>> > git://github.com/markus-oberhumer/linux).
>> >
>>
>> This doesn't look like a cgroup bug.
>
> Yes, it looks like a problem in usermodehelper. Rusty, it looks like
> usermodehelper can jam with OOM killer going wild. Any ideas? The
> original report is at
>
> https://lkml.org/lkml/2013/3/2/126
Is it really stuck, or just v. v. slow as it thrashes?
Like Tejun, I can't see how it would really get stuck...
Cheers,
Rusty.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>
Cc: Tommi Rantala <tt.rantala@gmail.com>,
containers@lists.linux-foundation.org, cgroups@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: cgroup_release_agent() hung task warnings
Date: Tue, 05 Mar 2013 12:28:04 +1100 [thread overview]
Message-ID: <87d2ved49n.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130304173358.GB30413@htj.dyndns.org>
Tejun Heo <tj@kernel.org> writes:
> (cc'ing Rusty Russell)
>
> On Mon, Mar 04, 2013 at 10:59:58AM +0800, Li Zefan wrote:
>> On 2013/3/3 3:23, Tommi Rantala wrote:
>> > Hello,
>> >
>> > I'm seeing the following hung task warnings when fuzzing the kernel
>> > with trinity (in a qemu virtual machine, as the root user), that I
>> > have not seen before with 3.8 or earlier. The kernel is
>> > b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50 (Merge tag
>> > 'lzo-update-signature-20130226' of
>> > git://github.com/markus-oberhumer/linux).
>> >
>>
>> This doesn't look like a cgroup bug.
>
> Yes, it looks like a problem in usermodehelper. Rusty, it looks like
> usermodehelper can jam with OOM killer going wild. Any ideas? The
> original report is at
>
> https://lkml.org/lkml/2013/3/2/126
Is it really stuck, or just v. v. slow as it thrashes?
Like Tejun, I can't see how it would really get stuck...
Cheers,
Rusty.
next prev parent reply other threads:[~2013-03-05 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 19:23 cgroup_release_agent() hung task warnings Tommi Rantala
2013-03-02 19:23 ` Tommi Rantala
2013-03-02 19:23 ` Tommi Rantala
[not found] ` <CA+ydwtrRAf5VW_iZYOjzmTv6Y0ebprXw_RfWVmR1okQOxQx=CA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-04 2:59 ` Li Zefan
2013-03-04 2:59 ` Li Zefan
[not found] ` <51340E2E.4070805-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-03-04 17:33 ` Tejun Heo
2013-03-04 17:33 ` Tejun Heo
2013-03-04 17:33 ` Tejun Heo
[not found] ` <20130304173358.GB30413-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-03-05 1:28 ` Rusty Russell
2013-03-05 1:28 ` Rusty Russell [this message]
2013-03-05 1:28 ` Rusty Russell
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=87d2ved49n.fsf@rustcorp.com.au \
--to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tt.rantala-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.