[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110329192434.GA10536@infradead.org>
Date: Tue, 29 Mar 2011 15:24:34 -0400
From: 'Christoph Hellwig' <hch@...radead.org>
To: Sean Noonan <Sean.Noonan@...sigma.com>
Cc: 'Michel Lespinasse' <walken@...gle.com>,
'Christoph Hellwig' <hch@...radead.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
Martin Bligh <Martin.Bligh@...sigma.com>,
Trammell Hudson <Trammell.Hudson@...sigma.com>,
Christos Zoulas <Christos.Zoulas@...sigma.com>,
"'linux-xfs@....sgi.com'" <linux-xfs@....sgi.com>,
Stephen Degler <Stephen.Degler@...sigma.com>,
"'linux-mm@...ck.org'" <linux-mm@...ck.org>
Subject: Re: XFS memory allocation deadlock in 2.6.38
Can you check if the brute force patch below helps? If it does I
still need to refine it a bit, but it could be that we are doing
an allocation under an xfs lock that could recurse back into the
filesystem. We have a per-process flag to disable that for normal
kmalloc allocation, but we lost it for vmalloc in the commit you
bisected the regression to.
Index: xfs/fs/xfs/linux-2.6/kmem.h
===================================================================
--- xfs.orig/fs/xfs/linux-2.6/kmem.h 2011-03-29 21:16:58.039224236 +0200
+++ xfs/fs/xfs/linux-2.6/kmem.h 2011-03-29 21:17:08.368223598 +0200
@@ -63,7 +63,7 @@ static inline void *kmem_zalloc_large(si
{
void *ptr;
- ptr = vmalloc(size);
+ ptr = __vmalloc(size, GFP_NOFS | __GFP_HIGHMEM, PAGE_KERNEL);
if (ptr)
memset(ptr, 0, size);
return ptr;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists