Re: cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Andy Whitcroft
On Tue, Dec 08, 2015 at 10:24:28AM -0500, Tejun Heo wrote: > Hello, Andy. > > On Tue, Dec 08, 2015 at 02:58:51PM +, Andy Whitcroft wrote: > > Converting this to a printk I was able to obtain confirmation that we are > > indeed seeing this go negative in some cases. > > > > Reverting the

Re: cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Tejun Heo
Hello, Andy. On Tue, Dec 08, 2015 at 02:58:51PM +, Andy Whitcroft wrote: > Converting this to a printk I was able to obtain confirmation that we are > indeed seeing this go negative in some cases. > > Reverting the above commit seems to resolve the early boot issues in > my testing. Fix

cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Andy Whitcroft
The commit below attempts to fix up pid controller charging: commit afcf6c8b75444382e0f9996157207ebae34a8848 Author: Tejun Heo Date: Thu Oct 15 16:41:53 2015 -0400 cgroup: add cgroup_subsys->free() method and use it to fix pids controller Since this change we are seeing system

Re: cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Tejun Heo
Hello, Andy. On Tue, Dec 08, 2015 at 02:58:51PM +, Andy Whitcroft wrote: > Converting this to a printk I was able to obtain confirmation that we are > indeed seeing this go negative in some cases. > > Reverting the above commit seems to resolve the early boot issues in > my testing. Fix

cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Andy Whitcroft
The commit below attempts to fix up pid controller charging: commit afcf6c8b75444382e0f9996157207ebae34a8848 Author: Tejun Heo Date: Thu Oct 15 16:41:53 2015 -0400 cgroup: add cgroup_subsys->free() method and use it to fix pids controller Since this change we are

Re: cgroup pids controller -- WARN_ON_ONCE triggering

2015-12-08 Thread Andy Whitcroft
On Tue, Dec 08, 2015 at 10:24:28AM -0500, Tejun Heo wrote: > Hello, Andy. > > On Tue, Dec 08, 2015 at 02:58:51PM +, Andy Whitcroft wrote: > > Converting this to a printk I was able to obtain confirmation that we are > > indeed seeing this go negative in some cases. > > > > Reverting the