lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Dec 2017 10:00:19 +0100
From:   Michal Hocko <>
To:     David Rientjes <>
Cc:     Tetsuo Handa <>,
        Andrew Morton <>,
        Andrea Arcangeli <>,,
Subject: Re: Multiple oom_reaper BUGs: unmap_page_range racing with exit_mmap

On Tue 05-12-17 23:48:21, David Rientjes wrote:
> I think this argues to do MMF_REAPING-style behavior at the beginning of 
> exit_mmap() and avoid reaping all together once we have reached that 
> point.  There are no more users of the mm and we are in the process of 
> tearing it down, I'm not sure that the oom reaper should be in the 
> business with trying to interfere with that.  Or are there actual bug 
> reports where an oom victim gets wedged while in exit_mmap() prior to 
> releasing its memory?

Something like that seem to work indeed. But we should better understand
what is going on here before adding new oom reaper specific kludges. So
let's focus on getting more information from your crashes first.
Michal Hocko

Powered by blists - more mailing lists