nvmeadm commit-firmware error reporting isn't working as intended
A while back, nvme_ioctl_firmware_commit() got the ability to return the error status (SCT and SC) from failed commands that were executed on its behalf. But there are still those many cases when the ioctl() can fail and return an error in errno without even having sent a command to the hardware, which consumers of this interface like nvmeadm(1M) can't easily detect as such.
Updated by Electric Monk 6 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit 8466ab889653be2119e4a8966b6bc4e2d5ee2fb6 Author: Hans Rosenfeld <firstname.lastname@example.org> Date: 2022-02-22T09:13:21.000Z 14507 nvmeadm shouldn't allow writing firmware to a read-only slot 1 14508 improve nvmeadm firmware reporting 14509 nvmeadm commit-firmware error reporting isn't working as intended Reviewed by: Guy Morrogh <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Reviewed by: Andy Giles <email@example.com> Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Reviewed by: Andy Fiddaman <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>