Hide Forgot
Created attachment 1228669 [details] Patch - take read lock Description of problem: Running any workload results in a core dump with this message: Illegal instruction (core dumped) Version-Release number of selected component (if applicable): filebench-1.4.9.1-5.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1. Use this sample workload file (any valid workload will do): set $dir=/tmp set $nfiles=100 set $meandirwidth=20 set $meanfilesize=16k set $iosize=1m set $nthreads=1 set mode quit firstdone define fileset name=bigfileset,path=$dir,size=$meanfilesize,entries=$nfiles,dirwidth=$meandirwidth,prealloc=100,paralloc define fileset name=destfiles,path=$dir,size=$meanfilesize,entries=$nfiles,dirwidth=$meandirwidth define process name=filereader,instances=1 { thread name=filereaderthread,memsize=10m,instances=$nthreads { flowop openfile name=openfile1,filesetname=bigfileset,fd=1 flowop readwholefile name=readfile1,fd=1,iosize=$iosize flowop createfile name=createfile2,filesetname=destfiles,fd=2 flowop writewholefile name=writefile2,fd=2,srcfd=1,iosize=$iosize flowop closefile name=closefile1,fd=1 flowop closefile name=closefile2,fd=2 } } echo "Copyfiles Version 3.0 personality successfully loaded" run 10 2. filebench -f <workload_file> Actual results: Core dumped just before reaching the "running" stage: Illegal instruction (core dumped) Expected results: Additional info: From the core file produced when this happens in a VM, it looks like it crashes in pthread_rwlock_unlock(). Looking at the source, the main thread tries to signal the worker threads with: /* Release the read lock, allowing threads to start */ (void) pthread_rwlock_unlock(&filebench_shm->shm_run_lock); ... but fails to actually take the lock at any point before doing that. See attached small patch for a proposed fix. Note that more recent upstream (currently at 1.5 alpha 3) does not have this particular issue.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.