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:   Fri, 15 Dec 2017 13:46:50 -0800 (PST)
From:   David Rientjes <>
To:     Michal Hocko <>
cc:     Andrew Morton <>,
        Andrea Arcangeli <>,
        Benjamin Herrenschmidt <>,
        Paul Mackerras <>,
        Oded Gabbay <>,
        Alex Deucher <>,
        Christian König <>,
        David Airlie <>,
        Joerg Roedel <>,
        Doug Ledford <>,
        Jani Nikula <>,
        Mike Marciniszyn <>,
        Sean Hefty <>,
        Dimitri Sivanich <>,
        Boris Ostrovsky <>,
        Jérôme Glisse <>,
        Paolo Bonzini <>,
        Radim Krčmář <>,,
Subject: Re: [patch v2 2/2] mm, oom: avoid reaping only for mm's with blockable
 invalidate callbacks

On Fri, 15 Dec 2017, Michal Hocko wrote:

> > This uses the new annotation to determine if an mm has mmu notifiers with
> > blockable invalidate range callbacks to avoid oom reaping.  Otherwise, the
> > callbacks are used around unmap_page_range().
> Do you have any example where this helped? KVM guest oom killed I guess?

KVM is the most significant one that we are interested in, but haven't had 
sufficient time to quantify how much of an impact this has other than to 
say it will certainly be non-zero.

The motivation was more to exclude mmu notifiers that have a reason to be 
excluded rather than a blanket exemption to make the oom reaper more 

Powered by blists - more mailing lists