If the ioengine specific parameter is given on the command line, unrelated value in thread_data.o will be corrupted unexpectedly. Specifically, if libaio specific parameter userspace_reap is given on the command line, thread_data.o.description will be set to 1.
This fixes it by passing the correct pointer of ioengine specific options to the command line parser. Signed-off-by: Akinobu Mita <[email protected]> --- * v2 - Update commit log to clarify that this problem only happens with the command line options. options.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/options.c b/options.c index 4b91f52..f26ff77 100644 --- a/options.c +++ b/options.c @@ -3603,7 +3603,7 @@ int fio_cmd_option_parse(struct thread_data *td, const char *opt, char *val) int fio_cmd_ioengine_option_parse(struct thread_data *td, const char *opt, char *val) { - return parse_cmd_option(opt, val, td->io_ops->options, td); + return parse_cmd_option(opt, val, td->io_ops->options, td->eo); } void fio_fill_default_options(struct thread_data *td) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
