From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Nelson Elhage <nelhage@ksplice.com>
Cc: Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: cgroup scheduling: Adding kthreadd to a non-RT cgroup can deadlock the kernel
Date: Wed, 05 Jan 2011 10:44:10 +0100 [thread overview]
Message-ID: <1294220650.2016.197.camel@laptop> (raw)
In-Reply-To: <20110105045447.GN23414@ksplice.com>
On Tue, 2011-01-04 at 23:54 -0500, Nelson Elhage wrote:
> Hi,
>
> I've found a bug where, on CONFIG_RT_GROUP_SCHED systems, adding the kthreadd
> task to a cgroup with cpu.rt_runtime_us = 0 (as some cgroup configuration
> scripts do, when they move all processes into a default cgroup), can result in
> deadlocks in the kernel.
IMHO its a bug to move kthreadd into a cgroup. Simply don't do that.
next prev parent reply other threads:[~2011-01-05 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 4:54 cgroup scheduling: Adding kthreadd to a non-RT cgroup can deadlock the kernel Nelson Elhage
2011-01-05 6:01 ` Mike Galbraith
2011-01-05 9:44 ` Peter Zijlstra [this message]
2011-01-05 15:02 ` Nelson Elhage
2011-01-05 15:18 ` Peter Zijlstra
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=1294220650.2016.197.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nelhage@ksplice.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