From: Theodore Tso <tytso@mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/ext/super.c:428
Date: Tue, 13 Jan 2009 20:44:34 -0500 [thread overview]
Message-ID: <20090114014434.GE14730@mit.edu> (raw)
In-Reply-To: <20090113164842.c6aa7095.akpm@linux-foundation.org>
On Tue, Jan 13, 2009 at 04:48:42PM -0800, Andrew Morton wrote:
> Well that's not good. I don't recall us making any changes which
> affect the orphan list handling. Perhaps "filesystem freeze: add error
> handling of write_super_lockfs/unlockfs", but only indirectly.
>
> Does Arjan's new async stuff play with filesystems at umount/shutdown
> time? Don't think so.
Well, Arjan's commit, efaee192: "async: make the final inode deletion
an asynchronous event", does change how inodes get deleted, and this
looks like a race where an inode is getting deleted during the umount.
So I would try reverting commit efaee192 and see if it fixes things
before starting a full bisect...
- Ted
next prev parent reply other threads:[~2009-01-14 1:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 0:36 kernel BUG at fs/ext/super.c:428 Pallipadi, Venkatesh
2009-01-14 0:48 ` Andrew Morton
2009-01-14 1:44 ` Theodore Tso [this message]
2009-01-14 2:48 ` Arjan van de Ven
2009-01-14 2:48 ` Arjan van de Ven
2009-01-14 4:40 ` Theodore Tso
2009-01-14 19:16 ` Pallipadi, Venkatesh
2009-01-14 19:16 ` Pallipadi, Venkatesh
2009-01-14 19:29 ` Peter Zijlstra
2009-01-14 19:38 ` Pallipadi, Venkatesh
2009-01-14 19:42 ` Peter Zijlstra
2009-01-14 19:48 ` Pallipadi, Venkatesh
2009-01-14 21:20 ` Theodore Tso
2009-01-21 20:10 ` Pallipadi, Venkatesh
2009-01-21 20:10 ` Pallipadi, Venkatesh
2009-01-24 7:36 ` Peter Zijlstra
2009-01-24 7:36 ` Peter Zijlstra
2009-01-26 16:39 ` Darren Hart
2009-01-26 16:39 ` Darren Hart
2009-01-26 16:46 ` Peter Zijlstra
2009-01-26 17:12 ` Darren Hart
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=20090114014434.GE14730@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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.