From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752099AbdBEKDa (ORCPT ); Sun, 5 Feb 2017 05:03:30 -0500 Received: from mx2.suse.de ([195.135.220.15]:40226 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751774AbdBEKD2 (ORCPT ); Sun, 5 Feb 2017 05:03:28 -0500 Date: Sun, 5 Feb 2017 11:03:21 +0100 From: Michal Hocko To: Trevor Cordes Cc: Mel Gorman , linux-kernel@vger.kernel.org, Joonsoo Kim , Minchan Kim , Rik van Riel , Srikar Dronamraju Subject: Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected) Message-ID: <20170205100319.GA22713@dhcp22.suse.cz> References: <20170120155553.gjv2x5eycvdudnil@techsingularity.net> <20170122184559.0b5c0fd8@pog.tecnopolis.ca> <20170123104858.gpjy25y2ogju3gkg@techsingularity.net> <20170125040246.5b211135@pog.tecnopolis.ca> <20170125120420.GM32377@dhcp22.suse.cz> <20170129165003.31bd8384@pog.tecnopolis.ca> <20170130075132.GB8443@dhcp22.suse.cz> <20170201032928.5d58a7c5@pog.tecnopolis.ca> <20170201101444.GJ5977@dhcp22.suse.cz> <20170203183654.1821addc@pog.tecnopolis.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170203183654.1821addc@pog.tecnopolis.ca> 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 Fri 03-02-17 18:36:54, Trevor Cordes wrote: > On 2017-02-01 Michal Hocko wrote: > > On Wed 01-02-17 03:29:28, Trevor Cordes wrote: > > > On 2017-01-30 Michal Hocko wrote: > > [...] > > > > Testing with Valinall rc6 released just yesterday would be a good > > > > fit. There are some more fixes sitting on mmotm on top and maybe > > > > we want some of them in finall 4.10. Anyway all those pending > > > > changes should be merged in the next merge window - aka 4.11 > > > > > > After 30 hours of running vanilla 4.10.0-rc6, the box started to go > > > bonkers at 3am, so vanilla does not fix the bug :-( But, the bug > > > hit differently this time, the box just bogged down like crazy and > > > gave really weird top output. Starting nano would take 10s, then > > > would run full speed, then when saving a file would take 5s. > > > Starting any prog not in cache took equally as long. > > > > Could you try with to_test/linus-tree/oom_hickups branch on the same > > git tree? I have cherry-picked "mm, vmscan: consider eligible zones in > > get_scan_count" which might be the missing part. > > I ran to_test/linus-tree/oom_hickups branch (4.10.0-rc6+) for 50 hours > and it does NOT have the bug! No problems at all so far. OK, that is definitely good to know. My other fix ("mm, vmscan: consider eligible zones in get_scan_count") was more theoretical than bug driven. I would add your Tested-by: Trevor Cordes unless you have anything against that. > So I think whatever to_test/linus-tree/oom_hickups has that since-4.9 > has that vanilla 4.10-rc6 does *not* have is indeed the fix. > > For my reference, and I know you guys aren't distro-specific, what is > the best way to get this fix into Fedora 24 (currently 4.9)? I will send this patch to 4.9+ stable as soon as it hits Linus tree. -- Michal Hocko SUSE Labs