xfs
[Top] [All Lists]

Re: Fw: [Bugme-new] [Bug 7662] New: AOE filesystem corruption on Alpha

To: "Ed L. Cashin" <ecashin@xxxxxxxxxx>
Subject: Re: Fw: [Bugme-new] [Bug 7662] New: AOE filesystem corruption on Alpha
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 15 Dec 2006 07:39:05 +0000
Cc: Andrew Morton <akpm@xxxxxxxx>, support@xxxxxxxxxx, Greg KH <greg@xxxxxxxxx>, boddingt@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, "bugme-daemon@xxxxxxxxxxxxxxxxxxxx" <bugme-daemon@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <20061214224826.GI10048@xxxxxxxxxx>
References: <20061209234305.c65b4e14.akpm@xxxxxxxx> <20061214224826.GI10048@xxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.2i
On Thu, Dec 14, 2006 at 05:48:26PM -0500, Ed L. Cashin wrote:
> ... and when using ext3 on the device.  However, we see problems when
> using XFS.  It appears that the XFS problem is unrelated, because the
> kernel's new lock debugging sees some problems that appear in the
> attached netconsole log.
> 
> XFS passes us a bio with a pointer to a page that has a reference
> count of zero which causes problems when __pskb_pull_tail does a put
> on the page.  With ext3, we only got pages with a reference count
> greater than zero.

It's a kmalloced page.  The same can happen with ext3 aswell, but only
when doing log recovery.  The last time this came up (vs iscsi) the
conclusion was that the driver needs to handle this case.  


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