mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Fedora Kernel Team <kernel-team@fedoraproject.org>,
	viro@ZenIV.linux.org.uk
Subject: inode->i_wb_list corruption.
Date: Tue, 6 Mar 2012 13:51:37 -0500	[thread overview]
Message-ID: <20120306185137.GA15881@redhat.com> (raw)

We've had three separate reports against 3.2.x recently where the linked list debugging
is getting tripped up by the prev->next pointer being null instead of pointing
to the current list entry while walking the i_wb_list

Call traces are slightly different each time, but all end up walking i_wb_list 
in dput -> d_kill -> i_put -> evict -> inode_wb_list_del

What protects that list ? It looks to be just bdi->wb.list_lock ?


full reports at:
https://bugzilla.redhat.com/show_bug.cgi?id=784741
https://bugzilla.redhat.com/show_bug.cgi?id=799229
https://bugzilla.redhat.com/show_bug.cgi?id=799692

	Dave


             reply	other threads:[~2012-03-06 18:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 18:51 Dave Jones [this message]
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
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
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=20120306185137.GA15881@redhat.com \
    --to=davej@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome