From: Frank Mayhar <fmayhar@google.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH V3] fix bb_prealloc_list corruption due to wrong group locking
Date: Mon, 16 Mar 2009 10:42:49 -0700 [thread overview]
Message-ID: <1237225369.3964.4.camel@bobble.smo.corp.google.com> (raw)
In-Reply-To: <49BE8C30.5030901@redhat.com>
On Mon, 2009-03-16 at 12:28 -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.
Eric, this may just be coincidence, but is it possible that this may be
related to our bitmap problem I described last week? We haven't tracked
it down yet but it certainly smells like a race and your fix corrects
just such a race in the same code.
The bitmap problem, btw, involves stuff apparently being marked as used
when it's really free (or something very much like that), ultimately
resulting in double frees.
--
Frank Mayhar <fmayhar@google.com>
Google, Inc.
next prev parent reply other threads:[~2009-03-16 17:43 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
2009-03-16 17:28 ` [PATCH V3] " Eric Sandeen
2009-03-16 17:42 ` Frank Mayhar [this message]
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=1237225369.3964.4.camel@bobble.smo.corp.google.com \
--to=fmayhar@google.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 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.