Re: Possible regression with cgroups in 3.11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2013/11/4 21:43, Markus Blank-Burian wrote:
>> synchronize_rcu() is a block operation and can keep us waiting for
>> a long period, so instead it's possible that usage never goes down
>> to 0 and we are in a dead loop.
> 
> Ok, I didn't think of that. Tracing shows that the function keeps
> looping. The last lines repeat indefinitely.
> 
...
>      kworker/3:5-7605  [003] ....   987.475678:
> mem_cgroup_reparent_charges: usage: 1568768
>      kworker/3:5-7605  [003] ....   987.478677:
> mem_cgroup_reparent_charges: usage: 1568768
>      kworker/3:5-7605  [003] ....   987.481675:
> mem_cgroup_reparent_charges: usage: 1568768

So it's much more likely this is a memcg bug rather than a cgroup bug.
I hope memcg guys could look into it, or you could do a git-bisect if
you can reliably reproduce the bug.

--
To unsubscribe from this list: send the line "unsubscribe cgroups" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux