From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <axboe@kernel.dk>
Subject: Re: fio signal 11
References: <BN3PR0401MB1457415455A5B0CEFB84447DF75F0@BN3PR0401MB1457.namprd04.prod.outlook.com>
 <CALjAwxhv8pCLJe0uT6PX1r7g4Mu=d8gA19VUFu0pUE9LkHTkrw@mail.gmail.com>
 <BN3PR0401MB145737C5D3670374BE0D29E5F7500@BN3PR0401MB1457.namprd04.prod.outlook.com>
From: Jens Axboe <axboe@kernel.dk>
Message-ID: <575CCF51.8020704@kernel.dk>
Date: Sat, 11 Jun 2016 20:56:17 -0600
MIME-Version: 1.0
In-Reply-To: <BN3PR0401MB145737C5D3670374BE0D29E5F7500@BN3PR0401MB1457.namprd04.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
To: Jeff Furlong <jeff.furlong@hgst.com>, Sitsofe Wheeler <sitsofe@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
List-ID: <fio@vger.kernel.org>

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.

-- 
Jens Axboe