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  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:   Tue, 24 Jan 2017 13:59:21 +0100
From:   Michal Hocko <>
To:     Mel Gorman <>
Cc:     Trevor Cordes <>,,
        Joonsoo Kim <>,
        Minchan Kim <>,
        Rik van Riel <>,
        Srikar Dronamraju <>
Subject: Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On Mon 23-01-17 10:48:58, Mel Gorman wrote:
> Unfortunately, even that will be race prone for GFP_NOFS callers as
> they'll effectively be racing to see if kswapd or another direct
> reclaimer can reclaim before the OOM conditions are hit. It is by
> design, but it's apparent that a __GFP_NOFAIL request can trigger OOM
> relatively easily as it's not necessarily throttled or waiting on kswapd
> to complete any work. I'll keep thinking about it.

Yes, we shouldn't trigger the OOM for GFP_NOFS as the memory reclaim is
really weaker. And that might really matter here. So the mmomt tree will
behave differently in this regards as we have [1]

Michal Hocko

Powered by blists - more mailing lists