From: Christoph Hellwig <hch@infradead.org>
To: "Ed L. Cashin" <ecashin@coraid.com>
Cc: Andrew Morton <akpm@osdl.org>,
support@coraid.com, Greg KH <greg@kroah.com>,
boddingt@optusnet.com.au, xfs@oss.sgi.com,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: Fw: [Bugme-new] [Bug 7662] New: AOE filesystem corruption on Alpha
Date: Fri, 15 Dec 2006 07:39:05 +0000 [thread overview]
Message-ID: <20061215073905.GA31821@infradead.org> (raw)
In-Reply-To: <20061214224826.GI10048@coraid.com>
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.
next prev parent reply other threads:[~2006-12-15 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061209234305.c65b4e14.akpm@osdl.org>
2006-12-14 22:48 ` Fw: [Bugme-new] [Bug 7662] New: AOE filesystem corruption on Alpha Ed L. Cashin
2006-12-15 7:39 ` Christoph Hellwig [this message]
2006-12-15 21:37 ` Ed L. Cashin
[not found] ` <20061218175300.GM23156@coraid.com>
[not found] ` <20061218222109.GA23156@coraid.com>
[not found] ` <20061218225343.GA30167@infradead.org>
2007-01-19 16:21 ` Re: bio pages with zero page reference count Ed L. Cashin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061215073905.GA31821@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=boddingt@optusnet.com.au \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=ecashin@coraid.com \
--cc=greg@kroah.com \
--cc=support@coraid.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox