Re: [PATCH] oom_reaper: don't call mmput_async() on uninitialized mm

2016-05-29 Thread Michal Hocko
On Fri 27-05-16 12:55:34, Andrew Morton wrote: > On Fri, 27 May 2016 10:10:59 +0200 Michal Hocko wrote: > > > On Fri 27-05-16 10:00:48, Arnd Bergmann wrote: > > > The change to the oom_reaper to hold a mutex inside __oom_reap_task() > > > accidentally started calling mmput_async() on the local >

Re: [PATCH] oom_reaper: don't call mmput_async() on uninitialized mm

2016-05-27 Thread Andrew Morton
On Fri, 27 May 2016 10:10:59 +0200 Michal Hocko wrote: > On Fri 27-05-16 10:00:48, Arnd Bergmann wrote: > > The change to the oom_reaper to hold a mutex inside __oom_reap_task() > > accidentally started calling mmput_async() on the local > > mm before that variable got initialized, as reported by

Re: [PATCH] oom_reaper: don't call mmput_async() on uninitialized mm

2016-05-27 Thread Michal Hocko
On Fri 27-05-16 10:00:48, Arnd Bergmann wrote: > The change to the oom_reaper to hold a mutex inside __oom_reap_task() > accidentally started calling mmput_async() on the local > mm before that variable got initialized, as reported by gcc > in linux-next: > > mm/oom_kill.c: In function '__oom_reap

[PATCH] oom_reaper: don't call mmput_async() on uninitialized mm

2016-05-27 Thread Arnd Bergmann
The change to the oom_reaper to hold a mutex inside __oom_reap_task() accidentally started calling mmput_async() on the local mm before that variable got initialized, as reported by gcc in linux-next: mm/oom_kill.c: In function '__oom_reap_task': mm/oom_kill.c:537:2: error: 'mm' may be used uninit