From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: xfstests failure generic/299
Date: Mon, 15 Apr 2013 13:15:38 +0400 [thread overview]
Message-ID: <87k3o4xih1.fsf@openvz.org> (raw)
In-Reply-To: <20130414224712.GC12542@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Sun, 14 Apr 2013 18:47:12 -0400, "Theodore Ts'o" <tytso@mit.edu> wrote:
> 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?
Yep, reproducible with -m32 compile option
>
> 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.
Actually fix is quite simple, after this everything works fine.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-fio-fix-segfault-on-32bits-platforms.patch --]
[-- Type: text/x-patch, Size: 780 bytes --]
>From 473842b2c1181245d3bfd1c5cfc6dbad1b695f79 Mon Sep 17 00:00:00 2001
From: root <root@sandy.qa.sw.ru>
Date: Mon, 15 Apr 2013 13:12:44 +0400
Subject: [PATCH] fio: fix segfault on 32bits platforms
---
stat.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/stat.c b/stat.c
index 2665952..f3bc63d 100644
--- a/stat.c
+++ b/stat.c
@@ -601,7 +601,7 @@ void show_thread_status(struct thread_stat *ts, struct group_run_stats *rs)
ts->short_io_u[0], ts->short_io_u[1],
ts->short_io_u[2]);
if (ts->continue_on_error) {
- log_info(" errors : total=%lu, first_error=%d/<%s>\n",
+ log_info(" errors : total=%llu, first_error=%d/<%s>\n",
ts->total_err_count,
ts->first_error,
strerror(ts->first_error));
--
1.7.1
[-- Attachment #3: Type: text/plain, Size: 36 bytes --]
>
> - Ted
next prev parent reply other threads:[~2013-04-15 9:15 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
2013-04-15 9:15 ` Dmitry Monakhov [this message]
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=87k3o4xih1.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.