From: Dave Jones <davej@redhat.com>
To: Yang Bai <hamo.by@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Fengguang Wu <fengguang.wu@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Fedora Kernel Team <kernel-team@fedoraproject.org>,
viro@zeniv.linux.org.uk, Christoph Hellwig <hch@infradead.org>
Subject: Re: inode->i_wb_list corruption.
Date: Fri, 9 Mar 2012 09:57:14 -0500 [thread overview]
Message-ID: <20120309145713.GA21543@redhat.com> (raw)
In-Reply-To: <CAO_0yfNt2jgiTPZn5NkwBAjQZtk+377gG71d6QOuXQrDHjdkEg@mail.gmail.com>
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).
Dave
next prev parent reply other threads:[~2012-03-09 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 18:51 inode->i_wb_list corruption Dave Jones
2012-03-06 21:03 ` Jan Kara
2012-03-07 7:26 ` Fengguang Wu
2012-03-07 10:42 ` Jan Kara
2012-03-09 8:34 ` Yang Bai
2012-03-09 14:57 ` Dave Jones [this message]
2012-03-09 15:19 ` Dave Jones
2012-03-09 16:14 ` Yang Bai
2012-03-09 18:00 ` Dave Jones
2012-03-09 20:08 ` Keith Packard
2012-03-09 20:19 ` Josh Boyer
2012-03-09 22:44 ` Keith Packard
2012-03-12 21:13 ` Josh Boyer
2012-03-12 21:27 ` David Woodhouse
2012-03-12 23:26 ` Dave Jones
2012-03-13 0:06 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2012-03-15 14:08 Petr Tesařík
2012-03-15 14:22 ` Dave Airlie
2012-03-15 14:49 ` Dave Jones
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=20120309145713.GA21543@redhat.com \
--to=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hamo.by@gmail.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.