From: Theodore Tso <tytso@mit.edu>
To: Christian Hesse <mail@eworm.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Oops with ext4 from 2.6.27-rc3
Date: Wed, 13 Aug 2008 18:01:00 -0400 [thread overview]
Message-ID: <20080813220100.GE6142@mit.edu> (raw)
In-Reply-To: <200808132307.07437.mail@eworm.de>
On Wed, Aug 13, 2008 at 11:07:06PM +0200, Christian Hesse wrote:
>
> Please look at the bottom of my last two mails... That was with your patch
> applied.
Sorry, I missed it. The new BUG seems to be a bug in the delayed
allocation code, specifically here, in fs/ext4/inode.c:ext4_da_release_space():
/* figure out how many metablocks to release */
BUG_ON(mdb > EXT4_I(inode)->i_reserved_meta_blocks);
mdb_free = EXT4_I(inode)->i_reserved_meta_blocks - mdb;
I've quickly looked at the code, and how i_reserved_meta_blocks gets
updated, and nothing *obviously* wrong is jumping out at me. Anyone
else have time to investigate this a bit more deeply?
- Ted
next prev parent reply other threads:[~2008-08-13 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 18:28 Oops with ext4 from 2.6.27-rc3 eworm
2008-08-13 20:10 ` Theodore Tso
2008-08-13 20:55 ` Christian Hesse
2008-08-13 21:04 ` Theodore Tso
2008-08-13 21:07 ` Christian Hesse
2008-08-13 22:01 ` Theodore Tso [this message]
2008-08-13 22:19 ` Eric Sandeen
2008-08-13 22:45 ` Theodore Tso
2008-08-14 4:12 ` Rishikesh K Rajak
2008-08-14 0:10 ` Mingming Cao
2008-08-14 1:51 ` Theodore Tso
2008-08-14 6:59 ` Christian Hesse
2008-08-14 14:58 ` Mingming Cao
2008-08-14 17:52 ` Aneesh Kumar K.V
[not found] ` <216e58580808132159y53fc5403xb52839e1be2186a6@mail.gmail.com>
2008-08-14 5:39 ` Rishikesh K Rajak
2008-08-14 6:13 ` Christian Hesse
2008-08-14 6:16 ` Rishikesh K Rajak
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 21:03 Christian Hesse
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=20080813220100.GE6142@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mail@eworm.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