Skip to content

oom, memcg: do not report racy no-eligible OOM

Michal Hocko linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 24 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2mm, oom: marks all killed tasks as oom victimsmm/oom_kill.c+6 -02 replies
2/2memcg: do not report racy no-eligible OOM tasksmm/memcontrol.c+13 -16 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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

Hi,
I have posted this as an RFC previously [1]. Tetsuo has pointed out some issues with the patch 1 which I have fixed hopefully. Other than that this is just a rebase on top of Linus tree.

The original cover:
this is a follow up for [2] 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 [2] 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.

Feedback is appreciated of course.

[1] http://lkml.kernel.org/r/[email protected]
[2] http://lkml.kernel.org/r/[email protected]