public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
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: Tue, 27 Aug 2013 14:58:14 +0200	[thread overview]
Message-ID: <20130827125814.GJ10995@rei.Home> (raw)
In-Reply-To: <1843973614.1971535.1377606877922.JavaMail.root@redhat.com>

Hi!
> > > > This should really work and I've been told by our filesystem guy that
> > > > this really looks like bug in the kernel (assuming that I haven't
> > > > overlooked something in the test source).
> > > 
> > > Do you know about any doc/source that says why it should work?
> > > In my search I only came across that man page, which seems to go in
> > > opposite way.
> > 
> > I simply asked Jan Kara.
> 
> I brought this to attention of some local FS guys as well.
> I found I can trigger it on physical system too (24CPU Amd Opteron) as long as
> dio_sparse runs on ext4. I couldn't do the same with xfs.
> 
> I could trigger it quite easily with kernels going back to 3.3 and also
> with latest upstream 3.11-rc7 just by running:
> env TMPDIR=/mnt/ext4 ./dio_sparse  -a 4k -w 4k -s 2k -n 2
> in loop for couple minutes.

I thinked about the strace a bit and it looks to me like some dirty
memory buffer was reused without being cleared (the reader seen
something that appeared to be part of the strace output that presumbly
was being saved to the disk). Which may be real bug because you may
happen to see content of a file (that is being written to the disk) you
have no permission to read. But you probably know that allready.

-- 
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

      parent reply	other threads:[~2013-08-27 12:58 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
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 [this message]

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=20130827125814.GJ10995@rei.Home \
    --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