From: Theodore Ts'o <tytso@mit.edu>
To: Dustin Lundquist <dustin@null-ptr.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:1234!
Date: Thu, 20 Jun 2013 12:34:06 -0400 [thread overview]
Message-ID: <20130620163406.GB4982@thunk.org> (raw)
In-Reply-To: <51C32BB1.5070902@null-ptr.net>
On Thu, Jun 20, 2013 at 09:20:01AM -0700, Dustin Lundquist wrote:
>
> Since the system is still half way responsive after this occurs, is
> there any other information I can gather after if occurs to aid in
> diagnosing this?
Hmm.... the only thing I can think of is to sprinkle in some
WARN_ON(irqs_disabled());
calls in various top-half routines in ext4 code, especially in
ext4_lookup() and ext4_find_entry(), and perhaps in the vfs layer to
see if we can figure out where the interrupts are getting disabled.
The fact that blkcipher_walk_done() was showing up in the stack trace
is certainly suspicious.
- Ted
next prev parent reply other threads:[~2013-06-20 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:41 kernel BUG at fs/buffer.c:1234! Dustin Lundquist
2013-06-19 18:55 ` Theodore Ts'o
2013-06-20 16:20 ` Dustin Lundquist
2013-06-20 16:34 ` Theodore Ts'o [this message]
2013-07-04 20:31 ` Dustin Lundquist
2013-07-08 14:12 ` Jan Kara
2013-07-10 4:05 ` Dustin Lundquist
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=20130620163406.GB4982@thunk.org \
--to=tytso@mit.edu \
--cc=dustin@null-ptr.net \
--cc=linux-ext4@vger.kernel.org \
/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.