From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752546AbdGEIUY (ORCPT ); Wed, 5 Jul 2017 04:20:24 -0400 Received: from mx2.suse.de ([195.135.220.15]:42347 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752502AbdGEIUW (ORCPT ); Wed, 5 Jul 2017 04:20:22 -0400 Date: Wed, 5 Jul 2017 10:20:19 +0200 From: Michal Hocko To: Tetsuo Handa Cc: hannes@cmpxchg.org, riel@redhat.com, akpm@linux-foundation.org, mgorman@suse.de, vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm, vmscan: do not loop on too_many_isolated for ever Message-ID: <20170705082018.GB14538@dhcp22.suse.cz> References: <201703102044.DBJ04626.FLVMFOQOJtOFHS@I-love.SAKURA.ne.jp> <201706300914.CEH95859.FMQOLVFHJFtOOS@I-love.SAKURA.ne.jp> <20170630133236.GM22917@dhcp22.suse.cz> <201707010059.EAE43714.FOVOMOSLFHJFQt@I-love.SAKURA.ne.jp> <20170630161907.GC9714@dhcp22.suse.cz> <201707012043.BBE32181.JOFtOFVHQMLOFS@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201707012043.BBE32181.JOFtOFVHQMLOFS@I-love.SAKURA.ne.jp> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat 01-07-17 20:43:56, Tetsuo Handa wrote: > Michal Hocko wrote: [...] > > It is really hard to pursue this half solution when there is no clear > > indication it helps in your testing. So could you try to test with only > > this patch on top of the current linux-next tree (or Linus tree) and see > > if you can reproduce the problem? > > With this patch on top of next-20170630, I no longer hit this problem. > (Of course, this is because this patch eliminates the infinite loop.) I assume you haven't seen other negative side effects, like unexpected OOMs etc... Are you willing to give your Tested-by? -- Michal Hocko SUSE Labs