Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>,
	Sitsofe Wheeler <sitsofe@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: fio signal 11
Date: Sat, 11 Jun 2016 21:30:00 -0600	[thread overview]
Message-ID: <575CD738.1050505@kernel.dk> (raw)
In-Reply-To: <575CCF51.8020704@kernel.dk>

On 06/11/2016 08:56 PM, Jens Axboe wrote:
> On 06/10/2016 12:42 PM, Jeff Furlong wrote:
>> Good point.  Here is the trace:
>>
>> [New LWP 59231]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib64/libthread_db.so.1".
>> Core was generated by `fio --name=test_job --ioengine=libaio
>> --direct=1 --rw=write --iodepth=32'.
>> Program terminated with signal 11, Segmentation fault.
>> #0  0x0000000000421e39 in regrow_log (iolog=0x7f828c0c5ad0) at
>> stat.c:1909
>> 1909        if (!cur_log) {
>>
>> (gdb) bt
>> #0  0x0000000000421e39 in regrow_log (iolog=0x7f828c0c5ad0) at
>> stat.c:1909
>> #1  0x000000000042d4df in regrow_logs (td=td@entry=0x7f8277de0000) at
>> stat.c:1965
>> #2  0x000000000040ca90 in wait_for_completions
>> (td=td@entry=0x7f8277de0000, time=time@entry=0x7fffcfb6b300) at
>> backend.c:446
>> #3  0x000000000045ade7 in do_io (bytes_done=<synthetic pointer>,
>> td=0x7f8277de0000) at backend.c:991
>> #4  thread_main (data=data@entry=0x264d450) at backend.c:1667
>> #5  0x000000000045cfec in run_threads (sk_out=sk_out@entry=0x0) at
>> backend.c:2217
>> #6  0x000000000045d2cd in fio_backend (sk_out=sk_out@entry=0x0) at
>> backend.c:2349
>> #7  0x000000000040d09c in main (argc=22, argv=0x7fffcfb6f638,
>> envp=<optimized out>) at fio.c:63
>
> That looks odd, thanks for reporting this. I'll see if I can get to this
> on Monday, if not, it'll have to wait until after my vacation... So
> while I appreciate people running -git and finding issues like these
> before they show up in a release, might be best to revert back to 2.2.11
> until I can get this debugged.

I take that back - continue using -git! Just pull a fresh copy, should
be fixed now.

Jan, the reporter is right, 2.11 works and -git does not. So I just ran
a quick bisect, changing the logging from every second to every 100ms to
make it reproduce faster. I don't have time to look into why yet, so I
just reverted the commit.

commit d7982dd0ab2a1a315b5f9859c67a02414ce6274f
Author: Jan Kara <jack@suse.cz>
Date:   Tue May 24 17:03:21 2016 +0200

     fio: Simplify forking of processes

-- 
Jens Axboe



  reply	other threads:[~2016-06-12  3:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 21:58 fio signal 11 Jeff Furlong
2016-06-10  7:17 ` Sitsofe Wheeler
2016-06-10 18:42   ` Jeff Furlong
2016-06-12  2:56     ` Jens Axboe
2016-06-12  3:30       ` Jens Axboe [this message]
2016-06-13 17:58         ` Jeff Furlong
2016-06-13 18:01           ` Jens Axboe
2016-06-13 18:04             ` Jeff Furlong
2016-06-13 19:21               ` Jeff Furlong
2016-06-13 19:23                 ` Jens Axboe
2016-06-13 19:34                   ` Jens Axboe
2016-06-13 20:55                     ` Jeff Furlong
2016-06-13 21:23                       ` Jens Axboe
2016-06-15 14:45         ` Jan Kara
2016-06-16  7:06           ` Jens Axboe
2016-07-20  5:08             ` Jan Kara
2016-07-25 15:21               ` Jens Axboe
2016-07-26  8:43                 ` Jan Kara
2016-07-26 14:17                   ` Jens Axboe
2016-07-26 18:33                     ` Jeff Furlong
2016-07-26 18:35                       ` Jens Axboe
2016-08-01 22:57                         ` Jeff Furlong
2016-08-02 21:03                           ` Jens Axboe
2016-08-03 14:55                           ` Jens Axboe
2016-08-03 15:02                             ` Jeff Furlong
2016-08-03 15:03                               ` Jens Axboe
2016-08-03 15:14                                 ` Jens Axboe
2016-08-03 15:29                                   ` Jeff Furlong

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=575CD738.1050505@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=jeff.furlong@hgst.com \
    --cc=sitsofe@gmail.com \
    /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