From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15231] kernel BUG at fs/ext4/inode.c:1852!
Date: Tue, 9 Feb 2010 18:27:44 GMT [thread overview]
Message-ID: <201002091827.o19IRiC5018525@demeter.kernel.org> (raw)
In-Reply-To: <bug-15231-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15231
--- Comment #8 from Theodore Tso <tytso@mit.edu> 2010-02-09 18:27:22 ---
Well, the BUG_ON getting tripped as reported in comment #1 in this bug is:
BUG_ON(mdblocks < EXT4_I(inode)->i_reserved_meta_blocks);
... and the commit 39bc680a does mess with how i_reserved_meta_blocks is
calculated.
@@ -1836,10 +1834,11 @@ repeat:
}
return -ENOSPC;
}
+ spin_lock(&EXT4_I(inode)->i_block_reservation_lock);
EXT4_I(inode)->i_reserved_data_blocks += nrblocks;
- EXT4_I(inode)->i_reserved_meta_blocks = mdblocks;
next prev parent reply other threads:[~2010-02-09 18:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 9:38 [Bug 15231] New: BUG: soft lockup - CPU#3 stuck for 61s bugzilla-daemon
2010-02-05 9:43 ` [Bug 15231] " bugzilla-daemon
2010-02-05 9:50 ` [Bug 15231] kernel BUG at fs/ext4/inode.c:1852! bugzilla-daemon
2010-02-09 1:05 ` bugzilla-daemon
2010-02-09 1:06 ` bugzilla-daemon
2010-02-09 3:52 ` bugzilla-daemon
2010-02-09 3:57 ` bugzilla-daemon
2010-02-09 18:09 ` bugzilla-daemon
2010-02-09 18:27 ` bugzilla-daemon [this message]
2010-02-09 18:30 ` bugzilla-daemon
2010-02-10 3:26 ` bugzilla-daemon
2010-02-11 3:53 ` bugzilla-daemon
2010-02-11 4:48 ` bugzilla-daemon
2010-02-11 5:13 ` bugzilla-daemon
2010-02-11 5:22 ` bugzilla-daemon
2010-02-12 3:29 ` bugzilla-daemon
2010-02-15 17:14 ` bugzilla-daemon
2010-02-16 0:49 ` bugzilla-daemon
2010-02-16 6:45 ` bugzilla-daemon
[not found] <bug-15231-13602@https.bugzilla.kernel.org/>
2012-05-14 15:06 ` bugzilla-daemon
2012-05-14 15:06 ` 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=201002091827.o19IRiC5018525@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.