projects
/
fio.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
io_u: tweak small content buffer scramble
[fio.git]
/
REPORTING-BUGS
diff --git
a/REPORTING-BUGS
b/REPORTING-BUGS
index c6150d141c024e4e5ba9b76daa61a46473f0a236..d8876ae6870f691f0e5a777b398d71b19203937e 100644
(file)
--- a/
REPORTING-BUGS
+++ b/
REPORTING-BUGS
@@
-2,8
+2,10
@@
Reporting a bug
---------------
If you notice anything that seems like a fio bug, please do send email
---------------
If you notice anything that seems like a fio bug, please do send email
-to the list (fio@vger.kernel.org, see README) about it. You'll need
-to report at least:
+to the list (fio@vger.kernel.org, see README) about it. If you are not
+running the newest release of fio, upgrading first is recommended.
+
+When reporting a bug, you'll need to include:
1) A description of what you think the bug is
2) Environment (Linux distro version, kernel version). This is mostly
1) A description of what you think the bug is
2) Environment (Linux distro version, kernel version). This is mostly
@@
-12,4
+14,8
@@
to report at least:
4) How to reproduce. Please include a full list of the parameters
passed to fio and the job file used (if any).
4) How to reproduce. Please include a full list of the parameters
passed to fio and the job file used (if any).
+A bug report can never have too much information. Any time information
+is left out and has to be asked for, it'll add to the turn-around time
+of getting to the bottom of it and committing a fix.
+
That's it!
That's it!