From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH/RFC] aiodio: make read_sparse use same mode as writers
Date: Wed, 21 Aug 2013 12:24:37 +0200 [thread overview]
Message-ID: <20130821102436.GA3894@rei> (raw)
In-Reply-To: <b02ceb0270268de40055e69232d12c3a3422f7f4.1376919310.git.jstancek@redhat.com>
Hi!
> Starting with 3.10 dio_sparse sporadically fails, because
> read() in read_sparse returns garbage and dio_sparse testcase
> fails with:
> dio_sparse 0 TINFO : Dirtying free blocks
> dio_sparse 0 TINFO : Starting I/O tests
> non zero buffer at buf[0] => 0xffffffaa,ffffffaa,ffffffaa,ffffffaa
> non-zero read at offset 0
> dio_sparse 0 TINFO : Killing childrens(s)
> dio_sparse 1 TFAIL : 1 children(s) exited abnormally
>
> Issue is that we have parent opening file as O_DIRECT and
> children trying to read from it without O_DIRECT, which is
> discouraged in man pages.
>
> open(2) says:
> "Applications should avoid mixing O_DIRECT and normal I/O to the same
> file, and especially to overlapping byte regions in the same file."
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> ---
The README in the testcases directory says that the tests explicitly
tests for consistency between buffered I/O and O_DIRECT.
I will consult some kernel guys if this was ever supported and we will
either remove the tests or try to find a bug in the kernel.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-08-21 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 13:38 [LTP] [PATCH/RFC] aiodio: make read_sparse use same mode as writers Jan Stancek
2013-08-20 3:13 ` Wanlong Gao
2013-08-20 6:34 ` Jan Stancek
2013-08-20 6:44 ` Wanlong Gao
2013-08-20 7:06 ` Jan Stancek
2013-08-21 10:24 ` chrubis [this message]
2013-08-21 13:41 ` chrubis
[not found] ` <92780376.1937886.1377095931551.JavaMail.root@redhat.com>
2013-08-21 15:06 ` chrubis
[not found] ` <1843973614.1971535.1377606877922.JavaMail.root@redhat.com>
2013-08-27 12:58 ` chrubis
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=20130821102436.GA3894@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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