xfs
[Top] [All Lists]

Re: XFS memory allocation deadlock in 2.6.38

To: Sean Noonan <Sean.Noonan@xxxxxxxxxxxx>
Subject: Re: XFS memory allocation deadlock in 2.6.38
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 23 Mar 2011 10:25:04 +1100
Cc: "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>, Martin Bligh <Martin.Bligh@xxxxxxxxxxxx>, Trammell Hudson <Trammell.Hudson@xxxxxxxxxxxx>
In-reply-to: <081DDE43F61F3D43929A181B477DCA95639B52E8@xxxxxxxxxxxxxxxxxxxx>
References: <081DDE43F61F3D43929A181B477DCA95639B52E8@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Fri, Mar 18, 2011 at 11:46:04AM -0400, Sean Noonan wrote:
> Using the attached program, we are able to reproduce this bug reliably.
> $ make vmtest
> $ ./vmtest /xfs/hugefile.dat $(( 16 * 1024 * 1024 * 1024 )) # vmtest 
> <path_to_file> <size_in_bytes>
> /xfs/hugefile.dat: mapped 17179869184 bytes in 33822066943 ticks
> 749660: avg 13339 max 234667 ticks
> 371945: avg 26885 max 281616 ticks
> ---
> At this point, we see the following on the console:
> [593492.694806] XFS: possible memory allocation deadlock in kmem_alloc 
> (mode:0x250)
> [593506.724367] XFS: possible memory allocation deadlock in kmem_alloc 
> (mode:0x250)
> [593524.837717] XFS: possible memory allocation deadlock in kmem_alloc 
> (mode:0x250)
> [593556.742386] XFS: possible memory allocation deadlock in kmem_alloc 
> (mode:0x250)

What is the configuration of the machine you are testing on? I can't
reproduce this on a current 2.6.39-tot tree on a 2p/2GB RAM VM that
has it's blockdev images on a single SATA drive....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>