From: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: 2.6.33-rc4 i686 clone function looping (seems real!)
Date: Thu, 21 Jan 2010 18:35:25 +0100 [thread overview]
Message-ID: <1264095325.4283.1198.camel@laptop> (raw)
In-Reply-To: <20100121171338.GA16904-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Thu, 2010-01-21 at 11:13 -0600, Serge E. Hallyn wrote:
> The culprit is e2912009fb7b715728311b0d8fe327a1432b3f79
> sched: Ensure set_task_cpu() is never called on blocked tasks
>
> If you mount both the ns and cpuset cgroups with this patch applied,
> then doing clone with CLONE_NEWPID, CLONE_NEWNET, etc, you get the
> hang. The hang is actually hard enough that alt-sysrq isn't helpful :)
> Still trying to figure out what is going on - Peter, any ideas offhand?
Does it replicate on x86_64 ?
/me looks at the NEWPID and NEWNET code
Hmm, I have an idea.. does it really need the ns cgroup stuff?
Let me try and come up with a debug patch...
next prev parent reply other threads:[~2010-01-21 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:04 2.6.33-rc4 i686 clone function looping (?) Jean-Marc Pigeon
[not found] ` <1263852243.4745.363.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-01-19 15:09 ` Serge E. Hallyn
[not found] ` <20100119150931.GA7708-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-19 16:00 ` 2.6.33-rc4 i686 clone function looping (seems real!) Jean-Marc Pigeon
[not found] ` <1263916851.4745.386.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-01-19 22:10 ` Serge E. Hallyn
2010-01-19 22:15 ` Serge E. Hallyn
2010-01-21 17:13 ` Serge E. Hallyn
[not found] ` <20100121171338.GA16904-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-21 17:35 ` Peter Zijlstra [this message]
2010-01-21 20:20 ` Serge E. Hallyn
2010-01-21 20:36 ` [RFC][PATCH] sched: Fix fork vs hotplug vs cpuset namespaces Peter Zijlstra
2010-01-21 20:36 ` Peter Zijlstra
2010-01-21 22:30 ` [tip:sched/urgent] " tip-bot for 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=1264095325.4283.1198.camel@laptop \
--to=peterz-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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.