From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757375Ab2CIPUn (ORCPT ); Fri, 9 Mar 2012 10:20:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53451 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757172Ab2CIPUm (ORCPT ); Fri, 9 Mar 2012 10:20:42 -0500 Date: Fri, 9 Mar 2012 10:19:51 -0500 From: Dave Jones To: Yang Bai , Jan Kara , Fengguang Wu , Linux Kernel , Fedora Kernel Team , viro@zeniv.linux.org.uk, Christoph Hellwig Subject: Re: inode->i_wb_list corruption. Message-ID: <20120309151951.GA30160@redhat.com> Mail-Followup-To: Dave Jones , Yang Bai , Jan Kara , Fengguang Wu , Linux Kernel , Fedora Kernel Team , viro@zeniv.linux.org.uk, Christoph Hellwig References: <20120306185137.GA15881@redhat.com> <20120306210307.GC8781@quack.suse.cz> <20120307072608.GA24087@localhost> <20120307104240.GB18658@quack.suse.cz> <20120309145713.GA21543@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120309145713.GA21543@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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