From: Ted Ts'o <tytso@mit.edu>
To: merll@web.de
Cc: linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953
Date: Sun, 4 Mar 2012 15:27:08 -0500 [thread overview]
Message-ID: <20120304202708.GA9087@thunk.org> (raw)
In-Reply-To: <bug-42859-13602@https.bugzilla.kernel.org/>
On Sun, Mar 04, 2012 at 02:39:09PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
>
> Messages "kernel BUG at fs/ext4/extents.c:1953" occur, which seem to be
> triggered when running certain processes (reproducible with init and gdm). The
> volume can be mounted without any apparent problems and e2fsck does not report
> any errors. Nevertheless, the file system may have been corrupted during an
> earlier system crash.
Would you be willing to apply the following patch, and then see which
inode number gets reported (and whether it is always the same inode
number or one that varies) and then report back the results of running
the following debugfs commands?
(assuming the inode number is 12345)
debugfs /dev/sdX
debugfs: stat <12345>
degbufs: ex <12345>
Thanks!!
- Ted
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 74f23c2..0393542 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -1949,7 +1949,13 @@ ext4_ext_put_in_cache(struct inode *inode, ext4_lblk_t block,
__u32 len, ext4_fsblk_t start)
{
struct ext4_ext_cache *cex;
- BUG_ON(len == 0);
+ if (unlikely(len == 0)) {
+ ext4_msg(inode->i_sb, KERN_CRIT,
+ "ext4_put_in_cache has len == 0: "
+ "ino %u, lblk %lu, pblk %llu", inode->i_ino,
+ block, start);
+ BUG_ON(1);
+ }
spin_lock(&EXT4_I(inode)->i_block_reservation_lock);
trace_ext4_ext_put_in_cache(inode, block, len, start);
cex = &EXT4_I(inode)->i_cached_extent;
next prev parent reply other threads:[~2012-03-04 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 14:39 [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953 bugzilla-daemon
2012-03-04 20:27 ` Ted Ts'o [this message]
2012-03-04 22:11 ` Matthias Erll
2012-03-05 1:51 ` Ted Ts'o
2012-04-04 14:59 ` [Bug 42859] " bugzilla-daemon
2012-06-13 15:14 ` bugzilla-daemon
2012-06-13 15:14 ` bugzilla-daemon
2020-03-11 12:17 ` bugzilla-daemon
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=20120304202708.GA9087@thunk.org \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=merll@web.de \
/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).