From: Eric Sandeen <sandeen@redhat.com>
To: jing zhang <zj.barak@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
Andreas Dilger <adilger@sun.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: [PATCH] ext4: BUG_ON triggered in ext4_mb_complex_scan_group()
Date: Sun, 04 Apr 2010 23:36:06 -0500 [thread overview]
Message-ID: <4BB968B6.1060005@redhat.com> (raw)
In-Reply-To: <m2uac8f92701004042130o76a81f3az89d538ebe0afea31@mail.gmail.com>
jing zhang wrote:
> From: Jing Zhang <zj.barak@gmail.com>
>
> Date: Mon Apr 5 12:10:50 2010
>
> BUG_ON is triggered at [line:1762] in ext4_mb_complex_scan_group(),
Do you have a test case which can trigger this BUG_ON?
-Eric
> and fix is to change the return value of mb_find_extent() if the
> needed extent can not be found. The fix can also be applied to other
> points where mb_find_extent() is called.
>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Cc: Andreas Dilger <adilger@sun.com>
> Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
> Signed-off-by: Jing Zhang <zj.barak@gmail.com>
> ---
> fs/ext4/mballoc.c | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index bba1282..fbb6899 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -1321,7 +1321,7 @@ static int mb_find_extent(struct ext4_buddy
> *e4b, int order, int block,
> ex->fe_len = 0;
> ex->fe_start = 0;
> ex->fe_group = 0;
> - return 0;
> + return -ENOSPC;
> }
>
> /* FIXME dorp order completely ? */
> @@ -1358,6 +1358,8 @@ static int mb_find_extent(struct ext4_buddy
> *e4b, int order, int block,
> }
>
> BUG_ON(ex->fe_start + ex->fe_len > (1 << (e4b->bd_blkbits + 3)));
> + if (needed > ex->fe_len)
> + return -ENOSPC;
> return ex->fe_len;
> }
>
> @@ -1758,7 +1760,8 @@ void ext4_mb_complex_scan_group(struct
> ext4_allocation_context *ac,
> break;
> }
>
> - mb_find_extent(e4b, 0, i, ac->ac_g_ex.fe_len, &ex);
> + if (0 > mb_find_extent(e4b, 0, i, ac->ac_g_ex.fe_len, &ex))
> + break;
> BUG_ON(ex.fe_len <= 0);
> if (free < ex.fe_len) {
> ext4_grp_locked_error(sb, e4b->bd_group,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-05 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 4:30 [PATCH] ext4: BUG_ON triggered in ext4_mb_complex_scan_group() jing zhang
2010-04-05 4:36 ` Eric Sandeen [this message]
2010-04-05 5:01 ` jing zhang
2010-04-07 15:31 ` tytso
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=4BB968B6.1060005@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
--cc=zj.barak@gmail.com \
/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).