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: Mon, 13 Jun 2016 13:34:17 -0600 [thread overview]
Message-ID: <575F0AB9.4090801@kernel.dk> (raw)
In-Reply-To: <575F0824.2050304@kernel.dk>
On 06/13/2016 01:23 PM, Jens Axboe wrote:
> On 06/13/2016 01:21 PM, Jeff Furlong wrote:
>> I took the fio 2.11 release and applied patch
>> 356014ff351c6eb69339652650af5f6af72e5c22 but it only created a
>> different error:
>>
>> [New LWP 131047]
>> [New LWP 131030]
>> [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 --io'.
>> Program terminated with signal 11, Segmentation fault.
>> #0 __flist_del (next=0x0, prev=0x0) at flist.h:86
>> 86 next->prev = prev;
>> (gdb) bt
>> #0 __flist_del (next=0x0, prev=0x0) at flist.h:86
>> #1 flist_del_init (entry=0xd609c0) at flist.h:109
>> #2 flush_log (log=<optimized out>, do_append=<optimized out>) at
>> iolog.c:989
>> #3 0x0000000000457a08 in finish_log (td=td@entry=0x7f4f0fb1f000,
>> log=0x7f4f23e04ad0, trylock=1) at iolog.c:1011
>> #4 0x0000000000457be5 in __write_log (try=<optimized out>,
>> log=<optimized out>, td=0x7f4f0fb1f000) at iolog.c:1309
>> #5 write_bandw_log (td=0x7f4f0fb1f000, try=<optimized out>,
>> unit_log=<optimized out>) at iolog.c:1377
>> #6 0x0000000000457efc in td_writeout_logs (unit_logs=false,
>> td=0x7f4f0fb1f000) at iolog.c:1440
>> #7 fio_writeout_logs (unit_logs=unit_logs@entry=false) at iolog.c:1461
>> #8 0x0000000000466a67 in helper_thread_main (data=0x7f4f23e04d90) at
>> helper_thread.c:135
>> #9 0x00007f4f25a5edf5 in start_thread () from /lib64/libpthread.so.0
>> #10 0x00007f4f255881ad in clone () from /lib64/libc.so.6
>
> Hang on, I think I know what the issue is. Just now running a test to
> prove that the fix is correct, then I'll commit it and reply.
Try current -git, I committed this:
http://git.kernel.dk/cgit/fio/commit/?id=1eb467fb0d2fc2ab41f12d9537184fc6ae95b48a
Hopefully that'll be the last logging bug, after it got rewritten...
--
Jens Axboe
next prev parent reply other threads:[~2016-06-13 19:34 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
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 [this message]
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=575F0AB9.4090801@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