From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH V2] fix bb_prealloc_list corruption due to wrong group locking
Date: Mon, 16 Mar 2009 22:42:40 +0530 [thread overview]
Message-ID: <20090316171240.GA16242@skywalker> (raw)
In-Reply-To: <49BE82A9.4000407@redhat.com>
On Mon, Mar 16, 2009 at 11:47:37AM -0500, Eric Sandeen wrote:
> This is for Red Hat bug 490026,
> EXT4 panic, list corruption in ext4_mb_new_inode_pa
>
> ext4_lock_group(sb, group) is supposed to protect this list for
> each group, and a common code flow to remove an album is like
> this:
>
> ext4_get_group_no_and_offset(sb, pa->pa_pstart, &grp, NULL);
> ext4_lock_group(sb, grp);
> list_del(&pa->pa_group_list);
> ext4_unlock_group(sb, grp);
>
> so it's critical that we get the right group number back for
> this prealloc context, to lock the right group (the one
> associated with this pa) and prevent concurrent list manipulation.
>
> however, ext4_mb_put_pa() passes in (pa->pa_pstart - 1) with a
> comment, /* -1 is to protect from crossing allocation group */
>
> This makes sense for the group_pa, where pa_pstart is advanced
> by the length which has been used (in ext4_mb_release_context()),
> and when the entire length has been used, pa_pstart has been
> advanced to the first block of the next group.
>
> However, for inode_pa, pa_pstart is never advanced; it's just
> set once to the first block in the group and not moved after
> that. So in this case, if we subtract one in ext4_mb_put_pa(),
> we are actually locking the *previous* group, and opening the
> race with the other threads which do not subtract off the extra
> block.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> ndex: linux-2.6/fs/ext4/mballoc.c
> ===================================================================
> --- linux-2.6.orig/fs/ext4/mballoc.c
> +++ linux-2.6/fs/ext4/mballoc.c
> @@ -3589,6 +3589,7 @@ static void ext4_mb_put_pa(struct ext4_a
> struct super_block *sb, struct ext4_prealloc_space *pa)
> {
> ext4_group_t grp;
> + ext4_fsblk_t grp_blk;
>
> if (!atomic_dec_and_test(&pa->pa_count) || pa->pa_free != 0)
> return;
> @@ -3603,8 +3604,12 @@ static void ext4_mb_put_pa(struct ext4_a
> pa->pa_deleted = 1;
> spin_unlock(&pa->pa_lock);
>
> - /* -1 is to protect from crossing allocation group */
> - ext4_get_group_no_and_offset(sb, pa->pa_pstart - 1, &grp, NULL);
> + grp_blk = pa->pa_pstart;
> + /* If linear, pa_pstart is in the next block group when pa is used up */
/* If linear, pa_pstart may be in the next block group when pa is used up */
^^^^^^^^^^
> + if (pa->pa_linear)
> + grp_blk--;
> +
> + ext4_get_group_no_and_offset(sb, grp_blk, &grp, NULL);
>
> /*
> * possible race:
>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
next prev parent reply other threads:[~2009-03-16 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 21:57 [PATCH] fix bb_prealloc_list corruption due to wrong group locking Eric Sandeen
2009-03-13 22:20 ` Eric Sandeen
2009-03-14 4:41 ` Eric Sandeen
2009-03-16 5:44 ` Aneesh Kumar K.V
2009-03-16 15:03 ` Eric Sandeen
2009-03-16 16:47 ` [PATCH V2] " Eric Sandeen
2009-03-16 17:12 ` Aneesh Kumar K.V [this message]
2009-03-16 17:28 ` [PATCH V3] " Eric Sandeen
2009-03-16 17:42 ` Frank Mayhar
2009-03-16 17:48 ` Eric Sandeen
2009-03-16 17:53 ` Frank Mayhar
2009-03-18 16:11 ` Frank Mayhar
2009-03-18 16:17 ` Eric Sandeen
2009-03-18 18:11 ` Theodore Tso
2009-03-17 3:30 ` 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=20090316171240.GA16242@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).