numam-spdk/examples
GangCao fcf4c5e426 bdev/fio: always set the engine_data to NULL
When initiating the io_u strcture from FIO, always
set the engine_data to NULL first as the io_u structure
is just malloced from FIO without specifically setting
to zero.

In the io_u free path, the engine_data field is checked
whether to NULL or not. To avoid mischeck issue, explicitly
set the engine_data to NULL at the beginning of the io_u
init path.

Change-Id: I52c8c251f36925650a44d14e35781bd8494ff358
Signed-off-by: GangCao <gang.cao@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/472916
Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: yidong0635 <dongx.yi@intel.com>
Reviewed-by: Ziye Yang <ziye.yang@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-11-06 14:49:00 +00:00
..
bdev bdev/fio: always set the engine_data to NULL 2019-11-06 14:49:00 +00:00
blob examples/blob: Optional VMD enumeration 2019-07-01 03:53:06 +00:00
ioat examples: rename ioat perf tool to ioat_perf 2019-05-22 14:51:01 +00:00
nvme bdev/fio: always set the engine_data to NULL 2019-11-06 14:49:00 +00:00
sock examples/sock: make hello_sock leverage net subsystem 2019-09-26 15:22:21 +00:00
vmd examples/vmd/led: LED management app 2019-10-24 17:04:04 +00:00
Makefile examples/vmd: VMD device usage example 2019-06-11 04:35:31 +00:00