xfs
[Top] [All Lists]

Re: ASSERT trip in XFS

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: ASSERT trip in XFS
From: Steve Lord <lord@xxxxxxx>
Date: Mon, 22 Jan 2001 16:08:05 -0600
Cc: Steve Lord <lord@xxxxxxx>, Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: Message from Andi Kleen <ak@xxxxxxx> of "Mon, 22 Jan 2001 22:54:10 +0100." <20010122225410.A14193@xxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
> On Mon, Jan 22, 2001 at 02:50:16PM -0600, Steve Lord wrote:
> > Daniel, can you try this patch, I do not have a sure fire way of
> > triggering this problem on my hardware. The problem appears to be
> > related to locking differences between Irix and Linux (again), the
> > strategy call in Irix is called with the buffer locked for the
> > duration, which means no one can change the underlying extents.
> > In the Linux case we have one page locked, and anything else in
> > the system can truncate the file out underneath us - we end up
> > allocating a new extent from scratch rather than turning a delalloc
> > into a real extent, this causes the extent to trip.
> 
> If you can get the linux inode semaphore it'll stop the truncates.

And deadlock when this code is callout out of a system call which already
has the inode lock....

I think this one is nasty!

Steve


> 
> -Andi



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