Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1701104
| From | Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Possible race condition in oom-killer |
| Date | 2017-08-01 16:20 +0200 |
| Message-ID | <u9GbE-52o-23@gated-at.bofh.it> (permalink) |
| References | <u8dEJ-4kJ-5@gated-at.bofh.it> <u8dY6-4rR-23@gated-at.bofh.it> <u8e7O-4Ks-47@gated-at.bofh.it> <u8rHI-5wl-7@gated-at.bofh.it> <u9Ejv-3Ut-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Michal Hocko wrote: > Once we merge [1] then the oom victim wouldn't > need to get TIF_MEMDIE to access memory reserves. > > [1] http://lkml.kernel.org/r/20170727090357.3205-2-mhocko@kernel.org False. We are not setting oom_mm to all thread groups (!CLONE_THREAD) sharing that mm (CLONE_VM). Thus, one thread from each thread group sharing that mm will have to call out_of_memory() in order to set oom_mm, and they will find task_will_free_mem() returning false due to MMF_OOM_SKIP already set, and after all goes to next OOM victim selection.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Possible race condition in oom-killer Michal Hocko <mhocko@kernel.org> - 2017-08-01 14:20 +0200
Re: Possible race condition in oom-killer Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2017-08-01 16:20 +0200
Re: Possible race condition in oom-killer Michal Hocko <mhocko@kernel.org> - 2017-08-01 16:50 +0200
csiph-web