Re: [PATCH] mm, oom: remove oom_lock from oom_reaper

2018-07-24 Thread David Rientjes
On Thu, 19 Jul 2018, Michal Hocko wrote: > From: Michal Hocko > > oom_reaper used to rely on the oom_lock since e2fe14564d33 ("oom_reaper: > close race with exiting task"). We do not really need the lock anymore > though. 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run >

Re: [PATCH] mm, oom: remove oom_lock from oom_reaper

2018-07-24 Thread David Rientjes
On Thu, 19 Jul 2018, Michal Hocko wrote: > From: Michal Hocko > > oom_reaper used to rely on the oom_lock since e2fe14564d33 ("oom_reaper: > close race with exiting task"). We do not really need the lock anymore > though. 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run >

[PATCH] mm, oom: remove oom_lock from oom_reaper

2018-07-19 Thread Michal Hocko
From: Michal Hocko oom_reaper used to rely on the oom_lock since e2fe14564d33 ("oom_reaper: close race with exiting task"). We do not really need the lock anymore though. 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run concurrently") has removed serialization with the exit path based

[PATCH] mm, oom: remove oom_lock from oom_reaper

2018-07-19 Thread Michal Hocko
From: Michal Hocko oom_reaper used to rely on the oom_lock since e2fe14564d33 ("oom_reaper: close race with exiting task"). We do not really need the lock anymore though. 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run concurrently") has removed serialization with the exit path based