[PATCH] nvme-loop: allow ctrl-loss-tmo for nvme-loop

Chaitanya Kulkarni Chaitanya.Kulkarni at wdc.com
Tue Sep 15 19:58:24 EDT 2020


On 9/15/20 16:12, Sagi Grimberg wrote:
>> Update nvme-loop transport with NVMF_OPT_CTRL_LOSS_TMO in allowed ops.
>> Without this patch following command fails on my setup :-
>>
>> nvme_fabrics: invalid parameter 'ctrl_loss_tmo=%d'
> But loop doesn't do anything with this param, why should it
> accept it?
> 

I think latest nvme-cli code adds ctrl_loss_tmo by default, which wasn't 
the case earlier (correct me if I'm wrong). nvme-loop doesn't have 
allowed tmo opts which makes param check failure in host/fabrics.c when
creating a controller.




More information about the Linux-nvme mailing list