From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org, vatsa@linux.vnet.ibm.com,
a.p.zijlstra@chello.nl
Subject: odd timing bug with cgroups?
Date: Fri, 13 Jun 2008 15:38:29 -0600 [thread overview]
Message-ID: <4852E8D5.3000503@nortel.com> (raw)
I'm seeing some odd behaviour in the case where a parent task forks a
child and then immediately attempts to put the child into a group.
It appears that there is a window after task creation where the child
task is in "limbo" such that the parent cannot put it into a group. If
I run the parent under "strace" or else sleep for a bit before trying to
put the child into a group, then everything works fine.
This seems odd...I would think that as soon as the fork() call returns
in the parent we should be able to put that task into a group.
I'm just starting to look at the code, but I thought I'd mention it in
case someone knows exactly where to look.
Chris
next reply other threads:[~2008-06-13 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:38 Chris Friesen [this message]
2008-06-14 4:15 ` odd timing bug with cgroups? Valdis.Kletnieks
2008-06-16 16:45 ` Chris Friesen
2008-06-16 21:29 ` odd timing bug with cgroups -- solved Chris Friesen
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=4852E8D5.3000503@nortel.com \
--to=cfriesen@nortel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vatsa@linux.vnet.ibm.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 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.