Re: oomkillers gone wild.

[David Rientjes]

On Fri, 8 Jun 2012, Thomas Gleixner wrote:

> > If we're leaking task_struct's, meaning that put_task_struct() isn't 
> > actually freeing them when the refcount goes to 0, then it's certainly not 
> > because of the oom killer which only sends a SIGKILL to the selected 
> > process.
> 
> I rather suspect, that this is a asymetry between get_ and
> put_task_struct and refcount just doesn't go to zero.
> 

We found an actual task_struct leak within put_task_struct() because of 
the free task notifiers during the 3.4 -rc cycle, so if kmemleak doesn't 
show anything then would it be possible to bisect the problem Dave?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/