linux-kernel - Re: inode->i_wb

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:	Fri, 9 Mar 2012 10:19:51 -0500
From:	Dave Jones <davej@...hat.com>
To:	Yang Bai <hamo.by@...il.com>, Jan Kara <jack@...e.cz>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Fedora Kernel Team <kernel-team@...oraproject.org>,
	viro@...iv.linux.org.uk, Christoph Hellwig <hch@...radead.org>
Subject: Re: inode->i_wb_list corruption.

On Fri, Mar 09, 2012 at 09:57:14AM -0500, Dave Jones wrote:
 > On Fri, Mar 09, 2012 at 04:34:57PM +0800, Yang Bai wrote:
 >  
 >  > I still want to know how to reproduce this bug. I add the following
 >  > patch to the kernel fc-16 3.2.9-1
 >  > 
 >  > So on every inode_wb_list_del, it will show the whole list.
 >  > 
 >  > and Doing while true; do touch a && rm -f a; done for almost one day
 >  > without any problem.
 >  > 
 >  > So How to reproduce it??
 > 
 > If it was that easy, I'd be bisecting it by now ;-)
 > 
 > This, like a bunch of other really weird bugs that we have no explanation for,
 > only seems to be being hit by a small minority of users.
 > 
 > One common thing seems to be that they were all quad core intel
 > boxes, with i915 graphics.
 > 
 > We have some reports of i915 causing memory corruption after suspend/hibernate,
 > but none of these reports mention whether they've done that (I just asked).

And with that, this arrived.. 
https://bugzilla.redhat.com/show_bug.cgi?id=788433#c3

I'm leaning strongly towards believing this is yet another case of i915
corrupting memory on resume.

	Dave

--
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/