lists.openwall.net   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, 11 Jan 2017 17:33:01 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     Ganapatrao Kulkarni <gpkulkarni@...il.com>, linux-mm@...ck.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: getting oom/stalls for ltp test cpuset01 with latest/4.9 kernel

On Wed 11-01-17 12:05:44, Vlastimil Babka wrote:
> On 01/11/2017 11:50 AM, Ganapatrao Kulkarni wrote:
> > Hi,
> > 
> > we are seeing OOM/stalls messages when we run ltp cpuset01(cpuset01 -I
> > 360) test for few minutes, even through the numa system has adequate
> > memory on both nodes.
> > 
> > this we have observed same on both arm64/thunderx numa and on x86 numa system!
> > 
> > using latest ltp from master branch version 20160920-197-gbc4d3db
> > and linux kernel version 4.9
> > 
> > is this known bug already?
> 
> Probably not.
> 
> Is it possible that cpuset limits the process to one node, and numa
> mempolicy to the other node?

No this shouldn't happen AFAICS. It is more likely that there is an
unrelated memory pressure happenning at the same time.
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ