| eda3a60699e1d96bb68875ef2169ca819eb8f4f9 |
|
20-May-2017 |
Elliott Hughes <enh@google.com> |
Update to fio-2.20.
Bug: N/A
Test: builds, seems to work
Change-Id: I455dcc898f00dc50ae5cb65d1b381982df5a51e0
/external/fio/filelock.c
|
| 3b9719fdce75714101d47b409d81681c6d671d65 |
|
26-Feb-2015 |
Jens Axboe <axboe@fb.com> |
Fix segfault due to bad munmap()
Bruce reports:
The latest code from git (built using clang) causes a segfault after printing the usage text when "./fio" is run:
[New LWP 100111]
No jobs(s) defined
fio-2.2.5-28-g93eeb
[usage text]
[New Thread 801c06400 (LWP 100111/fio)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 801c06400 (LWP 100111/fio)]
flist_empty (head=0x802000040) at flist.h:119
119 return head->next == head;
Current language: auto; currently minimal
(gdb) p head
$1 = (const struct flist_head *) 0x802000040
which is due to a bug in the filelock code, that uses
fio_mutex_remove() to remove the mutex. But that mutex is embedded
inside another mmap'ed region, hence we then segfault on later
deferencing pointers.
Signed-off-by: Jens Axboe <axboe@fb.com>
/external/fio/filelock.c
|
| c2e99542fdc504ef4c95d2c20655ff4d8d5c2e3f |
|
14-Jan-2015 |
Jens Axboe <axboe@fb.com> |
filelock: fix segfault on some use cases of log file locking
If we end up diving into a new smalloc pool, we could add
file lock references that meant nothing to other processes.
Fixes: 243bfe190245
Signed-off-by: Jens Axboe <axboe@fb.com>
/external/fio/filelock.c
|
| c180342e1293259ca8d23ed0298aa6c32815fee5 |
|
19-Dec-2014 |
Jens Axboe <axboe@fb.com> |
mutex: add __fio_mutex_remove()
We have to remember to free the condvar, so add a __fio_mutex_remove()
for cases that init a mutex inside an smalloc'ed region with
__fio_mutex_init().
Signed-off-by: Jens Axboe <axboe@fb.com>
/external/fio/filelock.c
|
| 243bfe190245a10e9d0981bf2a7c722edc4c43d4 |
|
02-Apr-2014 |
Jens Axboe <axboe@fb.com> |
iolog: don't serialize the writing of all logs
Serialize based on filename, so that independent logs can be
written at the same time. If the logs are big, this can take
a while to flush to disk. It's silly to have all jobs waiting
on each other, when they could write their own logs independently.
Signed-off-by: Jens Axboe <axboe@fb.com>
/external/fio/filelock.c
|