From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 191BD7F5D for ; Wed, 8 Jul 2015 09:06:48 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay2.corp.sgi.com (Postfix) with ESMTP id DC69C304053 for ; Wed, 8 Jul 2015 07:06:44 -0700 (PDT) Received: from smtpbguseast1.qq.com (smtpbguseast1.qq.com [54.204.34.129]) by cuda.sgi.com with ESMTP id VipyDD2o8DDFcFGA (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 08 Jul 2015 07:06:42 -0700 (PDT) Message-ID: <559D2E52.2070900@unitedstack.com> Date: Wed, 08 Jul 2015 22:06:10 +0800 From: juncheng bai MIME-Version: 1.0 Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push References: <20150707233743.GZ7943@dastard> In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Gavin Guo , Dave Chinner Cc: linux-kernel , xfs@oss.sgi.com Hi, All As far as I know, the patch b3f03bac8132207a20286d5602eda64500c19724 solves one case which big directory size. I am not very familiar with xfs, but I think why can't we use vmalloc when kmalloc fails? Thanks. -------------- juncheng bai On 2015/7/8 20:34, Gavin Guo wrote: > Hi Dave, > > On Wed, Jul 8, 2015 at 7:37 AM, Dave Chinner wrote: >> On Tue, Jul 07, 2015 at 05:29:43PM +0800, Gavin Guo wrote: >>> Hi all, >>> >>> Recently, we observed that there is the error message in >>> Ubuntu-3.13.0-48.80: >>> >>> "XFS: possible memory allocation deadlock in kmem_alloc (mode:0x8250)" >>> >>> repeatedly shows in the dmesg. Temporarily, our workaround is to tune the >>> parameters, such as, vfs_cache_pressure, min_free_kbytes, and dirty_ratio. >>> >>> And we also found that there are different error messages regarding the >>> hung tasks which happened in xfs_log_commit_cil and xlog_cil_push. >>> >>> The log is available at: http://paste.ubuntu.com/11835007/ >>> >>> The following link seems the same problem we suffered: >>> >>> XFS hangs with XFS: possible memory allocation deadlock in kmem_alloc >>> http://oss.sgi.com/archives/xfs/2015-03/msg00172.html >>> >>> I read the mail and found that there might be some modification regarding >>> to move the memory allocation outside the ctx lock. And I also read the >>> latest patch from February of 2015 to see if there is any new change >>> about that. Unfortunately, I didn't find anything regarding the change (may >>> be I'm not familiar with the XFS, so didn't find the commit). If it's >>> possible for someone who is familiar with the code to point out the commits >>> related to the bug if already exist or any status about the plan. >> >> No commits - the approach I thought we might be able to take to >> avoid the problem didn't work out. I have another idea of how we >> might solve the problem, but I haven't ad a chance to prototype it >> yet. >> >> Cheers, >> >> Dave. >> -- >> Dave Chinner >> david@fromorbit.com > > Really thanks for your information, I'll keep watching out the status. > > Thanks, > Gavin Guo > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs