From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: xfs@oss.sgi.com
Cc: vasily.isaenko@oracle.com
Subject: Re: [PATCH] generic: require filesize to be greater than fs block size in generic/240
Date: Fri, 06 Dec 2013 13:39:41 +0400 [thread overview]
Message-ID: <52A19B5D.8040802@oracle.com> (raw)
In-Reply-To: <1386321845-9221-1-git-send-email-stanislav.kholmanskikh@oracle.com>
On 12/06/2013 01:24 PM, Stanislav Kholmanskikh wrote:
> If we execute generic/240 on a fs which has its fs block size greater
> than 64k (for example, NFS), this test will fail with:
>
> io_submit failed: Invalid argument
>
> This will happen because in src/aio-dio-regress/aiodio_sparse2.c this
> expression
>
> num_aio = filesize / step;
>
> will set num_aio to 0 and this means that no io_setup() will happen
> before calling io_submit().
Actually, I mean "... no io_prep_pwrite() will happen before calling
io_submit()". It's a typo.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-06 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 9:24 [PATCH] generic: require filesize to be greater than fs block size in generic/240 Stanislav Kholmanskikh
2013-12-06 9:39 ` Stanislav Kholmanskikh [this message]
2013-12-11 6:55 ` 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=52A19B5D.8040802@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=vasily.isaenko@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox