All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	xfs-oss <xfs@oss.sgi.com>, Giel de Nijs <giel@vectorwise.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 10:15:09 -0600	[thread overview]
Message-ID: <4B645B0D.205@sandeen.net> (raw)
In-Reply-To: <20100130105501.GA22909@infradead.org>

Christoph Hellwig wrote:
> On Fri, Jan 29, 2010 at 02:05:46PM -0600, Eric Sandeen wrote:
>> Testcase from Giel de Nijs <giel@vectorwise.com>
>> on linux-ext4 list, ""Possible ext4 data corruption
>> with large files and async I/O," on 29 Jan 2010
>>
>> ext4 put byte offsets in a block offset u32 container
>> in the endio struct, so 4g wrapped to 0 leading to
>> data corruption when the unwritten extent did not
>> get converted.
> 
> There's various type messups in the test program that make it fail for

oops, thanks for checking.

> me on a 32-bit machine.  The patch below fixes it up, but it seems like
> we should rather add a variant of that code as aio_read/write commands
> to xfs_io instead of adding a new test program.

ok, that's probably better - again, though, it takes at least a release
cycle before most folks can test it.  But I guess that's not the end of
the world.

-Eric

> Index: xfstests-dev/src/aio-write.c
> ===================================================================
> --- xfstests-dev.orig/src/aio-write.c	2010-01-30 10:42:24.000000000 +0000
> +++ xfstests-dev/src/aio-write.c	2010-01-30 10:45:30.000000000 +0000
> @@ -42,7 +42,7 @@ void usage(void)
>  /*
>   * Scale value by kilo, mega, or giga.
>   */
> -loff_t scale_by_kmg(long long value, char scale)
> +long long scale_by_kmg(long long value, char scale)
>  {
>  switch (scale) {
>  	case 'g':
> @@ -69,7 +69,7 @@ switch (scale) {
>  int main(int argc, char ** argv)
>  {
>  	char filename[PATH_MAX];
> -	loff_t offset = 0;
> +	long long offset = 0;
>  	size_t length = 0;
>  	int seed = 0xFF;
>  	int queue_depth = 8;
> @@ -95,12 +95,12 @@ int main(int argc, char ** argv)
>  			seed = (int)strtol(optarg, &endp, 0);
>  			break;
>  		case 'o':
> -			offset = strtol(optarg, &endp, 0);
> -			offset = scale_by_kmg((long long)offset, *endp);
> +			offset = strtoll(optarg, &endp, 0);
> +			offset = scale_by_kmg(offset, *endp);
>  			break;
>  		case 'l':
>  			length = strtol(optarg, &endp, 0);
> -			length = scale_by_kmg((long long)length, *endp);
> +			length = scale_by_kmg(length, *endp);
>  			break;
>  		case 'v':
>  			verbose++;
> @@ -141,7 +141,8 @@ int main(int argc, char ** argv)
>  	io_prep_pwrite(&iocb, fd, buf, length, offset);
>  	iocblist[0] = &iocb;
>  	if (verbose)
> -		printf("submitting write of %zd bytes at offset %zd\n", length, offset);
> +		printf("submitting write of %zd bytes at offset %lld\n",
> +			length, offset);
>  	err = io_submit(io_ctx, 1, iocblist);
>  	if (err < 0) {
>  		printf("error submitting I/O requests: %s\n", strerror(-err));
> 


WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	Giel de Nijs <giel@vectorwise.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 10:15:09 -0600	[thread overview]
Message-ID: <4B645B0D.205@sandeen.net> (raw)
In-Reply-To: <20100130105501.GA22909@infradead.org>

Christoph Hellwig wrote:
> On Fri, Jan 29, 2010 at 02:05:46PM -0600, Eric Sandeen wrote:
>> Testcase from Giel de Nijs <giel@vectorwise.com>
>> on linux-ext4 list, ""Possible ext4 data corruption
>> with large files and async I/O," on 29 Jan 2010
>>
>> ext4 put byte offsets in a block offset u32 container
>> in the endio struct, so 4g wrapped to 0 leading to
>> data corruption when the unwritten extent did not
>> get converted.
> 
> There's various type messups in the test program that make it fail for

oops, thanks for checking.

> me on a 32-bit machine.  The patch below fixes it up, but it seems like
> we should rather add a variant of that code as aio_read/write commands
> to xfs_io instead of adding a new test program.

ok, that's probably better - again, though, it takes at least a release
cycle before most folks can test it.  But I guess that's not the end of
the world.

-Eric

> Index: xfstests-dev/src/aio-write.c
> ===================================================================
> --- xfstests-dev.orig/src/aio-write.c	2010-01-30 10:42:24.000000000 +0000
> +++ xfstests-dev/src/aio-write.c	2010-01-30 10:45:30.000000000 +0000
> @@ -42,7 +42,7 @@ void usage(void)
>  /*
>   * Scale value by kilo, mega, or giga.
>   */
> -loff_t scale_by_kmg(long long value, char scale)
> +long long scale_by_kmg(long long value, char scale)
>  {
>  switch (scale) {
>  	case 'g':
> @@ -69,7 +69,7 @@ switch (scale) {
>  int main(int argc, char ** argv)
>  {
>  	char filename[PATH_MAX];
> -	loff_t offset = 0;
> +	long long offset = 0;
>  	size_t length = 0;
>  	int seed = 0xFF;
>  	int queue_depth = 8;
> @@ -95,12 +95,12 @@ int main(int argc, char ** argv)
>  			seed = (int)strtol(optarg, &endp, 0);
>  			break;
>  		case 'o':
> -			offset = strtol(optarg, &endp, 0);
> -			offset = scale_by_kmg((long long)offset, *endp);
> +			offset = strtoll(optarg, &endp, 0);
> +			offset = scale_by_kmg(offset, *endp);
>  			break;
>  		case 'l':
>  			length = strtol(optarg, &endp, 0);
> -			length = scale_by_kmg((long long)length, *endp);
> +			length = scale_by_kmg(length, *endp);
>  			break;
>  		case 'v':
>  			verbose++;
> @@ -141,7 +141,8 @@ int main(int argc, char ** argv)
>  	io_prep_pwrite(&iocb, fd, buf, length, offset);
>  	iocblist[0] = &iocb;
>  	if (verbose)
> -		printf("submitting write of %zd bytes at offset %zd\n", length, offset);
> +		printf("submitting write of %zd bytes at offset %lld\n",
> +			length, offset);
>  	err = io_submit(io_ctx, 1, iocblist);
>  	if (err < 0) {
>  		printf("error submitting I/O requests: %s\n", strerror(-err));
> 

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

  reply	other threads:[~2010-01-30 16:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 20:05 [PATCH] xfstests 224: test aio hole-fill at 4g Eric Sandeen
2010-01-29 20:05 ` Eric Sandeen
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 10:55   ` Christoph Hellwig
2010-01-30 16:15   ` Eric Sandeen [this message]
2010-01-30 16:15     ` Eric Sandeen
2010-01-30 17:25     ` tytso
2010-01-30 17:25       ` tytso
2010-01-30 18:31       ` Eric Sandeen
2010-01-30 18:31         ` Eric Sandeen
2010-01-30 19:11         ` Christoph Hellwig
2010-01-30 19:11           ` Christoph Hellwig
2010-01-30 19:46           ` Eric Sandeen
2010-01-30 19:46             ` Eric Sandeen
2012-10-26 17:18 ` Rich Johnston
2012-10-26 17:52   ` Eric Sandeen

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=4B645B0D.205@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=giel@vectorwise.com \
    --cc=hch@infradead.org \
    --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 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.