Re: odd timing bug with cgroups -- solved

["Chris Friesen" <cfriesen@nortel.com>]

Chris Friesen wrote:

> I was thinking something like this as well, like maybe we can't move the 
> child to another group until it gets scheduled in once, or something 
> similar.

Well, it appears I was way off base.  My main task is SCHED_RR, and my 
child tasks put themselves into SCHED_OTHER.  I didn't have any realtime 
groups configured, so it was bailing out in the first conditional in 
cpu_cgroup_can_attach().

By also having the parent put the children into SCHED_OTHER, my testcase 
will handle both cases (parent or child runs first) and everything seems 
to be working fine.

Chris