From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933351AbcH2PHI (ORCPT ); Mon, 29 Aug 2016 11:07:08 -0400 Received: from mail-wm0-f44.google.com ([74.125.82.44]:36645 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933077AbcH2PHH (ORCPT ); Mon, 29 Aug 2016 11:07:07 -0400 Date: Mon, 29 Aug 2016 17:07:04 +0200 From: Michal Hocko To: Olaf Hering Cc: Andrew Morton , Markus Trippelsdorf , Arkadiusz Miskiewicz , Ralf-Peter Rohbeck , Jiri Slaby , Greg KH , Linus Torvalds , Vlastimil Babka , Joonsoo Kim , linux-mm@kvack.org, LKML Subject: Re: OOM detection regressions since 4.7 Message-ID: <20160829150703.GH2968@dhcp22.suse.cz> References: <20160822093707.GG13596@dhcp22.suse.cz> <20160822100528.GB11890@kroah.com> <20160822105441.GH13596@dhcp22.suse.cz> <20160822133114.GA15302@kroah.com> <20160822134227.GM13596@dhcp22.suse.cz> <20160822150517.62dc7cce74f1af6c1f204549@linux-foundation.org> <20160823074339.GB23577@dhcp22.suse.cz> <20160825071103.GC4230@dhcp22.suse.cz> <20160825071728.GA3169@aepfle.de> <20160829145203.GA30660@aepfle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160829145203.GA30660@aepfle.de> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 29-08-16 16:52:03, Olaf Hering wrote: > On Thu, Aug 25, Olaf Hering wrote: > > > On Thu, Aug 25, Michal Hocko wrote: > > > > > Any luck with the testing of this patch? > > I ran rc3 for a few hours on Friday amd FireFox was not killed. > Now rc3 is running for a day with the usual workload and FireFox is > still running. Is the patch (http://lkml.kernel.org/r/20160823074339.GB23577@dhcp22.suse.cz) applied? > Today I noticed the nfsserver was disabled, probably since months already. > Starting it gives a OOM, not sure if this is new with 4.7+. > Full dmesg attached. > [93348.306369] modprobe: page allocation failure: order:4, mode:0x26040c0(GFP_KERNEL|__GFP_COMP|__GFP_NOTRACK) ok so order-4 (COSTLY allocation) has failed because [...] > [93348.313778] Node 0 DMA: 1*4kB (U) 0*8kB 0*16kB 1*32kB (U) 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15908kB > [93348.313803] Node 0 DMA32: 13633*4kB (UME) 8035*8kB (UME) 890*16kB (UME) 10*32kB (U) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 133372kB > [93348.313822] Node 0 Normal: 14003*4kB (UME) 25*8kB (UME) 2*16kB (UM) 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 56244kB the memory is too fragmented for such a large allocation. Failing order-4 requests is not so severe because we do not invoke the oom killer if they fail. Especially without GFP_REPEAT we do not even try too hard. Recent oom detection changes shouldn't change this behavior. -- Michal Hocko SUSE Labs