diff options
| author | Michal Hocko <mhocko@suse.com> | 2018-12-28 00:39:57 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-12-28 12:11:52 -0800 |
| commit | 7056d3a37d2c6aaaab10c13e8e69adc67ec1fc65 (patch) | |
| tree | 74aeadd24b7ee5f20e44ffbd83c790021613c33e /mm/filemap.c | |
| parent | 7af7a8e19f0c5425ff639b0f0d2d244c2a647724 (diff) | |
| download | linux-7056d3a37d2c6aaaab10c13e8e69adc67ec1fc65.tar.gz linux-7056d3a37d2c6aaaab10c13e8e69adc67ec1fc65.tar.bz2 linux-7056d3a37d2c6aaaab10c13e8e69adc67ec1fc65.zip | |
memcg, oom: notify on oom killer invocation from the charge path
Burt Holzman has noticed that memcg v1 doesn't notify about OOM events via
eventfd anymore. The reason is that 29ef680ae7c2 ("memcg, oom: move
out_of_memory back to the charge path") has moved the oom handling back to
the charge path. While doing so the notification was left behind in
mem_cgroup_oom_synchronize.
Fix the issue by replicating the oom hierarchy locking and the
notification.
Link: http://lkml.kernel.org/r/20181224091107.18354-1-mhocko@kernel.org
Fixes: 29ef680ae7c2 ("memcg, oom: move out_of_memory back to the charge path")
Signed-off-by: Michal Hocko <mhocko@suse.com>
Reported-by: Burt Holzman <burt@fnal.gov>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com
Cc: <stable@vger.kernel.org> [4.19+]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/filemap.c')
0 files changed, 0 insertions, 0 deletions