mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: AIO, DIO fsx tests failures on 2.6.19-rc1-mm1
Date: Mon, 16 Oct 2006 13:38:19 -0700	[thread overview]
Message-ID: <1161031099.32606.14.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <4533E7E2.6010506@oracle.com>

On Mon, 2006-10-16 at 13:13 -0700, Zach Brown wrote:
> > Here is the easiest case to fix first :)
> > simple DIO wrote more than asked for :(
> > 
> > elm3b29:~ # /root/fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W
> > jnk
> > mapped writes DISABLED
> > truncating to largest ever: 0x32740
> > truncating to largest ever: 0x39212
> > truncating to largest ever: 0x3bae9
> > short write: 0x17000 bytes instead of 0x14000   <<<<<<
> 
> So the answer is that -rc1-mm1 doesn't quite have the most recent
> version of this patch.  Grab the final patch at the end of this post
> from Andrew:
> 
> 	http://lkml.org/lkml/2006/10/11/234
> 
> It fixes up a misunderstanding that came from
> generic_file_buffered_write()'s habit of adding its 'written' input into
> the amount of bytes it announces having written in its return value.
> 
> From mm-commits it looks like -mm2 will have the full patch.
> 

Hmm.. with that patch applied, I still have fsx failures.
This time read() returning -EINVAL. Are there any other fixes
missing in -mm ?

Thanks,
Badari

elm3b29:~ # /root/fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W
jnkI
mapped writes DISABLED
truncating to largest ever: 0x32740
truncating to largest ever: 0x39212
truncating to largest ever: 0x3bae9
truncating to largest ever: 0x3c1e3
truncating to largest ever: 0x3d1cd
truncating to largest ever: 0x3e8b8
truncating to largest ever: 0x3ed14
truncating to largest ever: 0x3f9c2
truncating to largest ever: 0x3ff9f
doread: read: Invalid argument
Segmentation fault



  reply	other threads:[~2006-10-16 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 15:42 Badari Pulavarty
2006-10-16 17:51 ` Zach Brown
2006-10-16 17:59   ` Badari Pulavarty
2006-10-16 20:13     ` Zach Brown
2006-10-16 20:38       ` Badari Pulavarty [this message]
2006-10-16 20:59         ` Andrew Morton
2006-10-16 21:21           ` Zach Brown
2006-10-17 22:31           ` Badari Pulavarty
2006-10-17 23:10             ` Andrew Morton
2006-10-17 23:38               ` Badari Pulavarty
2006-10-18 15:44             ` Chris Mason

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=1161031099.32606.14.camel@dyn9047017100.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach.brown@oracle.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

all inboxes | Powered by JetHome®