`nvme sanitize-log` differences with io_uring enabled

[tbzatek]

Bisected to #927 - we've started seeing first differences with libnvme-1.12 and io_uring enabled. Testing against local target and loop transport:

with io_uring:

# nvme sanitize-log /dev/nvme2
Sanitize Progress                      (SPROG) :  0
Sanitize Status                        (SSTAT) :  0
Sanitize Command Dword 10 Information (SCDW10) :  0
Estimated Time For Overwrite                   :  0
Estimated Time For Block Erase                 :  0
Estimated Time For Crypto Erase                :  0
Estimated Time For Overwrite (No-Deallocate)   :  0
Estimated Time For Block Erase (No-Deallocate) :  0
Estimated Time For Crypto Erase (No-Deallocate):  0

without io_uring, libnvme-1.11:

# nvme sanitize-log /dev/nvme2
NVMe status: Invalid Field in Command: A reserved coded value or an unsupported value in a defined field(0x6002)

Similar situation with nvme self-test-log.

[igaw]

Thanks for the report. I didn't expect this fallout using the io_uring interface. There is another related report on this linux-nvme/nvme-cli#2759

From a quick look, we don't check the result for each event.

[igaw]

FWIW, I plan to release a new version soon. Too many issues with 2.12...