mbox series

[RFC,0/2] oom, memcg: do not report racy no-eligible OOM

Message ID 20181022071323.9550-1-mhocko@kernel.org (mailing list archive)
Headers show
Series oom, memcg: do not report racy no-eligible OOM | expand

Message

Michal Hocko Oct. 22, 2018, 7:13 a.m. UTC 
Hi,
this is a follow up for [1] which has been nacked mostly because Tetsuo
was able to find a simple workload which can trigger a race where
no-eligible task is reported without a good reason. I believe the patch2
addresses that issue and we do not have to play dirty games with
throttling just because of the race. I still believe that patch proposed
in [1] is a useful one but this can be addressed later.

This series comprises 2 patch. The first one is something I meant to do
loooong time ago, I just never have time to do that. We need it here to
handle CLONE_VM without CLONE_SIGHAND cases. The second patch closes the
race.

I didn't get to test this throughly so it is posted as an RFC.

Feedback is appreciated of course.

[1] http://lkml.kernel.org/r/20181010151135.25766-1-mhocko@kernel.org