public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:52:03 -0600	[thread overview]
Message-ID: <498F9A53.3090409@sandeen.net> (raw)
In-Reply-To: <1234133120.12370.7.camel@champagne.cantina>

Alessandro Bono wrote:
> On Sun, 2009-02-08 at 17:42 -0500, Christoph Hellwig wrote:
>> On Sun, Feb 08, 2009 at 11:39:12PM +0100, Alessandro Bono wrote:
>>> On Sun, 2009-02-08 at 17:28 -0500, Christoph Hellwig wrote:
>>>> On Sat, Feb 07, 2009 at 02:06:13PM +0100, Alessandro Bono wrote:
>>>>> Feb  7 12:43:12 champagne kernel: [ 5828.167041] ------------[ cut
>>>>> here ]------------
>>>>> Feb  7 12:43:12 champagne kernel: [ 5828.167048] kernel BUG at
>>>>> fs/buffer.c:470!
>>>> Per
>>>> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-allstable.git;a=blob;f=fs/buffer.c;h=665d446b25bc034241ef54c3c6b1d239c0ccf0f9;hb=d5b562330ec766292a3ac54ae5e0673610bd5b3d
>>>>
>>>> line 470 in fs/buffer.c of 2.6.28.4 has a comment and no actual code.
>>>>
>>>> What additional patches do you have applied?
>>>>
>>> vanilla kernel
>>> no additional patches at all
>> Well, the 2.6.28.4 clearly doesn't have a bug there.  Can you
>> attach the fs/buffer.c you built the kernel from?
>>
> 
> 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);
   471		local_irq_save(flags);
   472		bit_spin_lock(BH_Uptodate_Lock, &first->b_state);
   473	
   474		clear_buffer_async_write(bh);
   475		unlock_buffer(bh);
   476		tmp = bh->b_this_page;
   477		while (tmp != bh) {
   478			if (buffer_async_write(tmp)) {


  reply	other threads:[~2009-02-09  2:52 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 [this message]
2009-02-09  2:53           ` Eric Sandeen
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=498F9A53.3090409@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