linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Frank Mayhar <fmayhar@google.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH V3] fix bb_prealloc_list corruption due to wrong group locking
Date: Wed, 18 Mar 2009 11:17:09 -0500	[thread overview]
Message-ID: <49C11E85.3040300@redhat.com> (raw)
In-Reply-To: <1237392694.31964.2.camel@bobble.smo.corp.google.com>

Frank Mayhar wrote:
> On Mon, 2009-03-16 at 10:53 -0700, Frank Mayhar wrote: 
>> On Mon, 2009-03-16 at 12:48 -0500, Eric Sandeen wrote:
>>> Hi Frank - I don't *think* so just because deleted items are poisoned
>>> and I would expect that we'd trip over a bad pointer in the corrupted
>>> list item as the first indicator of trouble... but I could be wrong.
>>>
>>> I think you said you could reproduce it, right?  So certainly worth
>>> testing with this fix I suppose.
>> Yeah, we're working on doing that now.  We're not running with a lot of
>> debugging turned on so we may or may not actually fall over if we try to
>> traverse freed (or just wrong) list entries.  If it isn't the same race,
>> though, then there's still one lurking in this code and that would be a
>> hell of a coincidence.
> 
> FYI we're running now with this patch in both a test and a production
> environment and haven't (yet) seen the bitmap inconsistency we were
> encountering regularly.  So far we have over 18 hours of runtime.  So,
> despite the enormous coincidence, our problem appears to be due to the
> same cause.
> 
> Thanks for the fix, Eric!

Good deal; I'll just trust that it's fixed, and maybe at some point I'll
sort out how they're related ;)

Thanks,
-Eric

  reply	other threads:[~2009-03-18 16:17 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
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 [this message]
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=49C11E85.3040300@redhat.com \
    --to=sandeen@redhat.com \
    --cc=fmayhar@google.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).