linux-kernel - Re: kernel BUG at fs/buffer.c:471! with 2.6.27.6

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]

Message-ID: <20081114175031.GA11737@infradead.org>
Date:	Fri, 14 Nov 2008 12:50:31 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Alessandro Bono <alessandro.bono@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-xfs@....sgi.com
Subject: Re: kernel BUG at fs/buffer.c:471! with 2.6.27.6

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/