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.
prev parent reply other threads:[~2013-03-05 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 19:23 cgroup_release_agent() hung task warnings Tommi Rantala
2013-03-04 2:59 ` Li Zefan
2013-03-04 17:33 ` Tejun Heo
2013-03-05 1:28 ` Rusty Russell [this message]
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@rustcorp.com.au \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.org \
--cc=tt.rantala@gmail.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