Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754500AbdCBJYm (ORCPT ); Thu, 2 Mar 2017 04:24:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41818 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754071AbdCBJYf (ORCPT ); Thu, 2 Mar 2017 04:24:35 -0500 Date: Thu, 2 Mar 2017 17:23:52 +0800 From: Xiong Zhou To: Michal Hocko Cc: Xiong Zhou , Anshuman Khandual , Christoph Hellwig , linux-xfs@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: mm allocation failure and hang when running xfstests generic/269 on xfs Message-ID: <20170302092352.r7dcykmddwue6san@XZHOUW.usersys.redhat.com> References: <20170301044634.rgidgdqqiiwsmfpj@XZHOUW.usersys.redhat.com> <20170302003731.GB24593@infradead.org> <20170302051900.ct3xbesn2ku7ezll@XZHOUW.usersys.redhat.com> <20170302084222.GA1404@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170302084222.GA1404@dhcp22.suse.cz> User-Agent: NeoMutt/20170206-195-7adf12 (1.7.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Thu, 02 Mar 2017 09:23:54 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3351 Lines: 134 On Thu, Mar 02, 2017 at 09:42:23AM +0100, Michal Hocko wrote: > On Thu 02-03-17 12:17:47, Anshuman Khandual wrote: > > On 03/02/2017 10:49 AM, Xiong Zhou wrote: > > > On Wed, Mar 01, 2017 at 04:37:31PM -0800, Christoph Hellwig wrote: > > >> On Wed, Mar 01, 2017 at 12:46:34PM +0800, Xiong Zhou wrote: > > >>> Hi, > > >>> > > >>> It's reproduciable, not everytime though. Ext4 works fine. > > >> On ext4 fsstress won't run bulkstat because it doesn't exist. Either > > >> way this smells like a MM issue to me as there were not XFS changes > > >> in that area recently. > > > Yap. > > > > > > First bad commit: > > > > > > commit 5d17a73a2ebeb8d1c6924b91e53ab2650fe86ffb > > > Author: Michal Hocko > > > Date: Fri Feb 24 14:58:53 2017 -0800 > > > > > > vmalloc: back off when the current task is killed > > > > > > Reverting this commit on top of > > > e5d56ef Merge tag 'watchdog-for-linus-v4.11' > > > survives the tests. > > > > Does fsstress test or the system hang ? I am not familiar with this > > code but If it's the test which is getting hung and its hitting this > > new check introduced by the above commit that means the requester is > > currently being killed by OOM killer for some other memory allocation > > request. > > Well, not exactly. It is sufficient for it to be _killed_ by SIGKILL. > And for that it just needs to do a group_exit when one thread was still > in the kernel (see zap_process). While I can change this check to > actually do the oom specific check I believe a more generic > fatal_signal_pending is the right thing to do here. I am still not sure > what is the actual problem here, though. Could you be more specific > please? It's blocking the test and system-shutdown. fsstress wont exit. For anyone interested, a simple ugly reproducer: cat > fst.sh < local.config < -- > Michal Hocko > SUSE Labs