From: Linus Torvalds <torvalds@linux-foundation.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Kernel BUG] ext4 for v2.6.32 round II
Date: Wed, 30 Sep 2009 18:57:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0909301847030.6996@localhost.localdomain> (raw)
In-Reply-To: <20091001014128.GA2092@phenom2.trippelsdorf.de>
On Thu, 1 Oct 2009, Markus Trippelsdorf wrote:
>
> Running latest git I get the following kernel BUG message:
>
> ------------[ cut here ]------------
> Kernel BUG at ffffffff810efa89 [verbose debug info unavailable]
You really shouldn't turn off verbose debug info unless you are _really_
tight on memory in some embedded device. It's not that complex, nor does
it use a lot of memory, and it makes the error report much harder to
figure out when the verbose debug output information isn't available.
But in this case I can do it by just looking at the function/offset:
> RIP: 0010:[<ffffffff810efa89>] [<ffffffff810efa89>] ext4_num_dirty_pages+0x113/0x213
The only BUG_ON() that seems relevant in that function (at least with the
config I tried with) ends up being
fs/ext4/inode.c:1184
in my sources, which is from "page_buffers(page)", which has a
BUG_ON(!PagePrivate(page));
in it. And that would have been much easier to figure out if you had had
CONFIG_DEBUG_BUGVERBOSE enabled..
Now over to the ext4 people to actually hopefully _solve_ the bug. Maybe
bisection would help.
Linus
next prev parent reply other threads:[~2009-10-01 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 5:25 [GIT PULL] ext4 for v2.6.32 round II Theodore Ts'o
2009-10-01 1:41 ` [Kernel BUG] " Markus Trippelsdorf
2009-10-01 1:57 ` Linus Torvalds [this message]
2009-10-01 2:15 ` Markus Trippelsdorf
2009-10-01 3:01 ` Theodore Tso
2009-10-01 3:47 ` Markus Trippelsdorf
2009-10-01 6:40 ` Theodore Tso
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=alpine.LFD.2.01.0909301847030.6996@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).