linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: xfstests failure generic/299
Date: Sun, 14 Apr 2013 18:47:12 -0400	[thread overview]
Message-ID: <20130414224712.GC12542@thunk.org> (raw)
In-Reply-To: <87sj2uokzc.fsf@openvz.org>

On Sat, Apr 13, 2013 at 01:09:27PM +0400, Dmitry Monakhov wrote:
> >      Run fio with random aio-dio pattern
> >      
> >      Start fallocate/truncate loop
> >     +./common/rc: line 2055:  3353 Segmentation fault      "$@" >>
> Yes, this is known issue. I probably use recent fio.git/HEAD
> Jens does a good job on developing fio, but he tend to commit random
> untested crap to his git. So stability is worse than it should be.
> I have golden-good commit (aeb32dfccbd05) which works for me, and suggest
> to use it.

Hmm... I just tried recompiling fio to git commit version
aeb32dfccbd05, and it's blowing up with a seg fault as well.

One thing about my test environment is that I'm building xfstests and
fio on a 32-bit x86 environemnt (because that way I can use an 32-bit
kernel, and because when I use a 64-bit kernel I stress test the
64-bit compatibility code paths).  Perhaps this has something to do
with it?

Unfortunately, I don't have the time to debug this, so at least for
now I'm going to exclude generic/299 from my automated test runs.

    	      	 	 	     	  - Ted

  reply	other threads:[~2013-04-14 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 21:03 xfstests failure generic/299 Theodore Ts'o
2013-04-13  9:09 ` Dmitry Monakhov
2013-04-14 22:47   ` Theodore Ts'o [this message]
2013-04-15  9:15     ` Dmitry Monakhov
2013-04-15 18:43       ` Theodore Ts'o
2013-04-16  8:20         ` Dmitry Monakhov

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=20130414224712.GC12542@thunk.org \
    --to=tytso@mit.edu \
    --cc=dmonakhov@openvz.org \
    --cc=linux-ext4@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).