linux-ext4 - Re: xfstests failure generic/299

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130414224712.GC12542@thunk.org>
Date:	Sun, 14 Apr 2013 18:47:12 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: xfstests failure generic/299

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html