All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Alain Renaud <arenaud@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfstest: test corruption with multi extent in PAGE.
Date: Fri, 13 Jul 2012 13:23:28 -0500	[thread overview]
Message-ID: <500067A0.2010809@sgi.com> (raw)
In-Reply-To: <4FFFF528.8060909@sgi.com>

On 07/13/12 05:15, Alain Renaud wrote:
> Since I got no feedback on the updated version let me send it again.
>
> xfstest: test corruption with multi extent in PAGE.
>
> Test using extsize/resvspace to create a file with multiple extent in
> one PAGE.
> This show an error in the block conversion from unwritten to real.
> As a result we tag raw disk block as valid(3-4)
> and valid data as unwritten(5-6)
>
> On an x86_64 machine the page should look like this.
>
> buffer content
> 0 empty b_state = 0
> 1 DATA b_state = 0x1023
> 2 DATA b_state = 0x1023
> 3 empty b_state = 0
> 4 empty b_state = 0
> 5 DATA b_state = 0x1023
> 6 DATA b_state = 0x1023
> 7 empty b_state = 0
>
> Signed-off-by: Alain Renaud <arenaud@sgi.com>

Tested with and without commit 7d0fa3ecba2f12ceef93fffe615e5dd9b50bb794
Looks good.

Reviewed-by: Mark Tinguely <tinguely@sgi.com>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-07-13 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 18:58 [PATCH 0/1] xfstest: using extsize cause corruption with multi buffer page Alain Renaud
2012-06-01 18:58 ` [PATCH 1/1] " Alain Renaud
2012-06-05  9:13   ` Dave Chinner
2012-06-05 12:22     ` Alain Renaud
2012-07-13 10:15       ` [PATCH v2] xfstest: test corruption with multi extent in PAGE Alain Renaud
2012-07-13 18:23         ` Mark Tinguely [this message]
     [not found] <20120710082318.685263546@sgi.com>
2012-07-10  8:32 ` Alain Renaud
2012-07-17  7:20   ` Christoph Hellwig

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=500067A0.2010809@sgi.com \
    --to=tinguely@sgi.com \
    --cc=arenaud@sgi.com \
    --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 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.