From: Eric Sandeen <sandeen@sandeen.net>
To: Alessandro Bono <alessandro.bono@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-xfs <linux-xfs@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4
Date: Sun, 08 Feb 2009 20:53:54 -0600 [thread overview]
Message-ID: <498F9AC2.2020703@sandeen.net> (raw)
In-Reply-To: <498F9A53.3090409@sandeen.net>
Eric Sandeen wrote:
> Alessandro Bono wrote:
..
>> sure, attached
>
> Well, that seems to not be from the kernel you were running; there is no
> BUG() on line 470:
>
> $ cat -n buffer.c | grep -8 " 470"
> 462 bdevname(bh->b_bdev, b));
> 463 }
> 464 set_bit(AS_EIO, &page->mapping->flags);
> 465 set_buffer_write_io_error(bh);
> 466 clear_buffer_uptodate(bh);
> 467 SetPageError(page);
> 468 }
> 469
> 470 first = page_buffers(page);
oh, oops :) it's probably this BUG():
#define page_buffers(page) \
({ \
BUG_ON(!PagePrivate(page)); \
-Eric
next prev parent reply other threads:[~2009-02-09 2:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 13:06 XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4 Alessandro Bono
2009-02-08 22:16 ` Dave Chinner
2009-02-08 23:24 ` Alessandro Bono
2009-02-09 10:33 ` Peter Zijlstra
2009-02-08 22:28 ` Christoph Hellwig
2009-02-08 22:39 ` Alessandro Bono
2009-02-08 22:42 ` Christoph Hellwig
2009-02-08 22:45 ` Alessandro Bono
2009-02-09 2:52 ` Eric Sandeen
2009-02-09 2:53 ` Eric Sandeen [this message]
2009-02-09 7:53 ` Christoph Hellwig
2009-02-09 9:02 ` Alessandro Bono
2009-02-10 10:43 ` Dave Chinner
2009-02-10 10:53 ` Alessandro Bono
2009-02-11 21:47 ` Alessandro Bono
2009-02-12 9:47 ` Alessandro Bono
2009-02-26 16:58 ` Jan Kara
2009-02-26 16:59 ` Jan Kara
2009-02-27 9:22 ` Alessandro Bono
2009-02-27 19:44 ` Alessandro Bono
2009-03-02 13:36 ` Jan Kara
2009-03-02 15:04 ` Alessandro Bono
2009-03-11 17:04 ` 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=498F9AC2.2020703@sandeen.net \
--to=sandeen@sandeen.net \
--cc=alessandro.bono@gmail.com \
--cc=hch@infradead.org \
--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