Re: Fio 2.0 coming (was "Re: Recent changes")

[Jens Axboe <axboe@kernel.dk>]

On 2011-10-15 15:59, Jens Axboe wrote:
> On 2011-10-15 14:55, Bruce Cran wrote:
>>
>> On 15 Oct 2011, at 13:44, Jens Axboe wrote:
>>
>>> Please try current -git, it should work now.
>>
>> Thanks, it's fixed.
>>
>> I can crash the client by pressing ctrl-c on the server:
>>
>>> ./fio -S
>> fio: server listening on 0.0.0.0:8765
>>  and ^C> 
>> ^^^^ there seems to be a random "and" printed?
>>
>>> ./fio -C localhost examples/tiobench-example
>>
>> ...
>>
>> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
>> <muon> 
>> Assertion failed: (cmdret->opcode == cmd.opcode), function fio_net_recv_cmd, file server.c, line 187.
>>
>> Program received signal SIGABRT, Aborted.
>> [Switching to Thread 28301140 (LWP 100220/initial thread)]
>> 0x281e7207 in kill () from /lib/libc.so.7
>> (gdb) bt
>> #0  0x281e7207 in kill () from /lib/libc.so.7
>> #1  0x280eb377 in raise () from /lib/libthr.so.3
>> #2  0x281e5d3a in abort () from /lib/libc.so.7
>> #3  0x281ce0c6 in __assert () from /lib/libc.so.7
>> #4  0x08074f8e in fio_net_recv_cmd (sk=3) at server.c:187
>> #5  0x08077f95 in fio_handle_clients () at client.c:779
>> #6  0x08051033 in exec_run () at fio.c:1779
>> #7  0x08051be1 in main (argc=4, argv=0xbfbfec04, envp=Error accessing memory address 0xb: Bad address.
>> ) at fio.c:1904
>> (gdb) 
> 
> OK, I'll take a look at that one. You are a good tester :-)
> 
> The assert itself is a fragmented packet, where a later fragment does
> not match the initial opcode. Must be due to a read error not being
> handled correctly.

Added attempt at failing naturally when that happens, does it reproduce
now?

-- 
Jens Axboe