From: Sachin Sant <sachinp@in.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: EXT4: kernel BUG at fs/ext4/mballoc.c:1721!
Date: Fri, 04 Sep 2009 13:57:47 +0530 [thread overview]
Message-ID: <4AA0CF83.8060405@in.ibm.com> (raw)
In-Reply-To: <20090903112003.GA13105@skywalker.linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
> Can you try this patch ?
>
Thanks for the patch Aneesh.
I have executed the tests several times against this patch
and haven't seen this issue. So at this point the patch looks good.
Tested-by : Sachin Sant <sachinp@in.ibm.com>
Will execute the tests few times more just to be doubly sure about this.
Thanks
-Sachin
> commit 43149bc800a6ae88b7d984558403e8d8cb045138
> Author: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Date: Thu Sep 3 16:47:27 2009 +0530
>
> ext4: check for good group with alloc_sem held
>
> We need to make sure we check for good group with alloc_sem
> held to make sure we prevent a parallel addition of new blocks
> to the group via resize.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index cd25846..4623555 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2029,13 +2029,6 @@ repeat:
> goto out;
> }
>
> - /*
> - * If the particular group doesn't satisfy our
> - * criteria we continue with the next group
> - */
> - if (!ext4_mb_good_group(ac, group, cr))
> - continue;
> -
> err = ext4_mb_load_buddy(sb, group, &e4b);
> if (err)
> goto out;
>
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-09-04 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 8:16 EXT4: kernel BUG at fs/ext4/mballoc.c:1721! Sachin Sant
2009-09-03 11:20 ` Aneesh Kumar K.V
2009-09-04 8:27 ` Sachin Sant [this message]
2009-09-04 8:49 ` Aneesh Kumar K.V
2009-09-04 12:52 ` Andreas Dilger
2009-09-07 9:35 ` Aneesh Kumar K.V
2009-09-07 9:38 ` [PATCH -V2 1/3] ext4: move ext4_mb_init_group around Aneesh Kumar K.V
2009-09-07 9:38 ` [PATCH -V2 2/3] ext4: check for need init flag in ext4_mb_load_buddy Aneesh Kumar K.V
2009-09-07 9:38 ` [PATCH -V2 3/3] ext4: Clarify the locking details in mballoc Aneesh Kumar K.V
2009-09-10 3:53 ` 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=4AA0CF83.8060405@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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).