From: Christoph Hellwig <hch@infradead.org>
To: Alessandro Bono <alessandro.bono@gmail.com>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:471! with 2.6.27.6
Date: Fri, 14 Nov 2008 12:50:31 -0500 [thread overview]
Message-ID: <20081114175031.GA11737@infradead.org> (raw)
In-Reply-To: <gfjqlf$kpt$1@ger.gmane.org>
On Fri, Nov 14, 2008 at 12:24:19PM +0000, Alessandro Bono wrote:
> Hi all
>
> second time I hit this bug, first time with 2.6.26.6 (reported to xfs ml
> without response)
> Condition are similar: rsync from remote server via ssh to a local usb hd
> with a xfs filesystem but connection this time is with a wired ethernet
> not wifi
> Tell me if you need other info
>
> kernel BUG at fs/buffer.c:471!
In 2.6.27.6 line 471 in fs/buffer.c is inside write and looks like this:
first = page_buffers(page)
and page_buffers is defined as:
#define page_buffers(page) \
({ \
BUG_ON(!PagePrivate(page)); \
((struct buffer_head *)page_private(page)); \
})
So we get a page without page_private set.
Now XFS always creates buffers in writepage when it doesn't have those
yet using the VFS helper create_empty_buffers which calls
attach_page_buffers, which sets the page private flag.
Given that the binary 3d driver always caused random VM problems can you
try to reproduce it with one loaded?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-11-14 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 12:24 kernel BUG at fs/buffer.c:471! with 2.6.27.6 Alessandro Bono
2008-11-14 17:50 ` Christoph Hellwig [this message]
2008-11-15 13:44 ` Alessandro Bono
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=20081114175031.GA11737@infradead.org \
--to=hch@infradead.org \
--cc=alessandro.bono@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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