xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: crash with latest code drop.

from [Peter Leckie] [Permanent Link][Original]
To: Peter Leckie <pleckie@xxxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: crash with latest code drop.
From: Peter Leckie <pleckie@xxxxxxx>
Date: Wed, 15 Oct 2008 13:47:06 +1000
In-reply-to: <20081015011857.GS10716@disturbed>
References: <48F54C20.8060704@sgi.com> <20081015011857.GS10716@disturbed>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (X11/20080707)
Dave Chinner wrote:
Can you confirm that the xfs_inode has either the I_RECLAIM or
I_RECLAIMABLE flag set on it when the panic occurred? If this
is the case, then the patch below will probably fix it.
Yep XFS_IRECLAIMABLE is set, I'll give the patch a test and get back to you.

Thanks,
Pete


[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode, Christoph Hellwig
Next by Date:  Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode, Lachlan McIlroy
Previous by Thread:  Re: crash with latest code drop., Dave Chinner
Next by Thread:  Attribution of patches in the git tree..., Dave Chinner
Indexes:  [Date] [Thread] [Top] [All Lists]