Some bugs about command line parameters

From: Erwan Velu <erwan_at_seanodes.com>
Date: Thu, 19 Jul 2007 14:23:23 +0200

Hey folks,
I'm running fio 1.16.6 on a x86 system using a Mandriva 2007.0.

I tried some "stupid" command line and it leads to segfault or "double
free or corruption" glibc errors.

I just created a simple job file like :
[erwan_at_r1 fio]$ cat asimplejob.fio
[global]
rw=read
size=16m

[job1]
description="Read Seq 16k O/Direct"
bs=16k
direct=1
numjobs=1

[job2]
description="Read Seq 128k O/Direct"
bs=128k
direct=1
numjobs=1

Then I did the following command lines :

fio /home/erwan/fio/asimplejob.fio /home/erwan/fio/asimplejob.fio -> a
did my tab completion twice :/

job1: (g=0): rw=read, bs=16K-16K/16K-16K, ioengine=sync, iodepth=1
job2: (g=0): rw=read, bs=128K-128K/128K-128K, ioengine=sync, iodepth=1
job1: (g=1): rw=read, bs=16K-16K/16K-16K, ioengine=sync, iodepth=1
job2: (g=1): rw=read, bs=128K-128K/128K-128K, ioengine=sync, iodepth=1
*** glibc detected *** fio: double free or corruption (!prev):
0x0806c200 ***
Then the glibc show the backtrace.

I also tried another stupid command line like:

fio /home/erwan/fio/asimplejob.fio /dev/sda5 -> Sounds stupid too I agree ;)
it looks like fio had opened the device sda5 and tried to read it to
find a job description.
After a while, I can see :

fio: option <\̶_[̶=\̶w\̶9[̶\̶\[̶[̶[̶\̶\̶d\̶> outside of
job section
Bad option \̶9[̶\̶\̶̶[̶Z̶[̶\̶Z̶Z̶GU̶OU̶oU̶fU̶v[̶
fio: job dropped
Erreur de segmentation (core dumped)

I know this is not so critical but at the time fio comes more & more
known like a good io stress tool, "stupid" users or miswritting will
become more & more common ;)))

Erwan,
Received on Thu Jul 19 2007 - 14:23:23 CEST

This archive was generated by hypermail 2.2.0 : Thu Jul 19 2007 - 14:30:01 CEST