| Jens Axboe | fb0480b | 2007-03-28 09:16:08 +0200 | [diff] [blame] | 1 | Reporting a bug |
| 2 | --------------- |
| 3 | |
| 4 | If you notice anything that seems like a fio bug, please do send email |
| Elliott Hughes | eda3a60 | 2017-05-19 18:53:02 -0700 | [diff] [blame] | 5 | to the list (fio@vger.kernel.org, see README) about it. If you are not |
| 6 | running the newest release of fio, upgrading first is recommended. |
| 7 | |
| 8 | When reporting a bug, you'll need to include: |
| Jens Axboe | fb0480b | 2007-03-28 09:16:08 +0200 | [diff] [blame] | 9 | |
| 10 | 1) A description of what you think the bug is |
| 11 | 2) Environment (Linux distro version, kernel version). This is mostly |
| 12 | needed if it's a build bug. |
| Jens Axboe | d793f80 | 2012-10-20 19:55:50 +0200 | [diff] [blame] | 13 | 3) The output from fio --version. |
| Jens Axboe | fb0480b | 2007-03-28 09:16:08 +0200 | [diff] [blame] | 14 | 4) How to reproduce. Please include a full list of the parameters |
| 15 | passed to fio and the job file used (if any). |
| 16 | |
| Elliott Hughes | eda3a60 | 2017-05-19 18:53:02 -0700 | [diff] [blame] | 17 | A bug report can never have too much information. Any time information |
| 18 | is left out and has to be asked for, it'll add to the turn-around time |
| 19 | of getting to the bottom of it and committing a fix. |
| 20 | |
| Jens Axboe | fb0480b | 2007-03-28 09:16:08 +0200 | [diff] [blame] | 21 | That's it! |