From: Eric Sandeen <sandeen@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>, ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] xfstests 241: run parallel dbench
Date: Wed, 18 Aug 2010 09:26:32 -0500 [thread overview]
Message-ID: <4C6BED98.10203@redhat.com> (raw)
In-Reply-To: <20100818114507.GS10429@dastard>
Dave Chinner wrote:
> On Tue, Aug 17, 2010 at 02:39:41PM -0500, Eric Sandeen wrote:
>> ext4 was corrupting inode table bitmaps due to a mishmash of
>> atomic & nonatomic bitops. This got broken twice and fixed
>> twice; let's add a test.
>>
>> On a 4-way box this reliably ends up with a corrupted filesystem
>> if we get it wrong (upstream as of 2.6.35 at least is fine again)
>>
>> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
>
> Looks good, except it's missing a 241.out file for the golden
> output.
grr "guilt add" :)
Thanks, will add that to the commit.
-Eric
> Cheers,
>
> Dave.
prev parent reply other threads:[~2010-08-18 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 19:39 [PATCH] xfstests 241: run parallel dbench Eric Sandeen
2010-08-18 11:45 ` Dave Chinner
2010-08-18 14:26 ` Eric Sandeen [this message]
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=4C6BED98.10203@redhat.com \
--to=sandeen@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xfs@oss.sgi.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).