[PATCH nvme-cli] nvme: check MUD support before firmware commit

[Tokunori Ikegami]

On 2026/05/20 15:22, 顾泽兵 wrote:
> Yes, we observed this in our production environment last week. For the
> SOLIDIGM SB5PH27X076T Gen5 NVMe device, when upgrading the firmware from
> G70YG472 to G70YG473, nvme-cli printed the following error after Firmware
> Commit:
>
>      identify-ctrl: No such device or address
>
> It reproduced 100% in our environment for this device and this firmware update
> path. I suspect this is because the firmware activation takes long enough for
> the post-command Identify Controller command to hit the controller reset window.
>
> After applying this patch, the extra identify-ctrl error after the successful
> Firmware Commit disappeared.
>
> Environment:
>    - kernel: Linux 6.12
>    - OS: Debian 13.2
>    - nvme-cli: 2.13
Understood.
> There is no public issue report yet.
>
> The user-visible nvme-cli output was:
>
>      Success committing firmware action:3 slot:1
>      identify-ctrl: No such device or address
>
> We did not find any kernel error messages in dmesg around the failure. The only
> user-visible error was printed by nvme-cli.
Noted this also. Thank you.
Reviewed-by: Tokunori Ikegami <ikegami.t at gmail.com>