linux-kernel - Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Feb 2009 10:47:57 +0100
From:	Alessandro Bono <alessandro.bono@...il.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	linux-xfs <linux-xfs@....sgi.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4

On Tue, 2009-02-10 at 21:43 +1100, Dave Chinner wrote:
> On Mon, Feb 09, 2009 at 02:53:08AM -0500, Christoph Hellwig wrote:
> > On Sun, Feb 08, 2009 at 11:45:20PM +0100, Alessandro Bono wrote:
> > > sure, attached
> > 
> > That would be a missing PagePrivate bit in page_buffers() called from
> > end_buffer_async_write.  PG_private can only be cleared via drop_buffers
> > which requires the page not having PG_writeback set which must be
> > set until end_buffer_async_write is done.  Very strange, and all this
> > is generic code without xfs involvement.  Did this happen once
> > or can you reproduce it?
> 
> Hmmmm - i wonder if this has anything to do with the writeback fixes
> that went into 2.6.28.2? Alessandro, can you revert to 2.6.28.1 (not
> plain 2.6.28) and see if you can reproduce the problem?

another test another bug
kernel 2.6.29-rc4-git4 with DEBUG_PAGEALLOC and CONFIG_DEBUG_LIST
enabled (idea taken from a totally unrelated mail from Ingo Molnar to
catch a memory corruption), usual bug attached
2.6.27 from ubuntu not survived to rsync

btw my first report of a similar problem was with a kernel 2.6.26.6 but
at time I was using binary driver for my radeon card and Christoph
suggest me that I have to recreate problem without any binary driver
maybe it's not a recent regression, it's simply easier to hit with a
newer kernel

I don't have abandoned idea of a hardware problem but I don't know how
to be sure

any suggestion?

thanks

> 
> Cheers,
> 
> Dave.
-- 
---
Cordiali Saluti
Alessandro Bono

View attachment "bug-2.6.29-rc4-git4" of type "text/plain" (5645 bytes)