nvme-cli connect regression

Sagi Grimberg sagi at grimberg.me
Tue Apr 15 14:14:28 PDT 2025



On 15/04/2025 12:01, Daniel Wagner wrote:
> On Mon, Apr 14, 2025 at 01:29:42AM +0300, Sagi Grimberg wrote:
>> Was this resolved?
> I've added a retry loop in libnvme when the write to /dev/nvme-fabrics
> returns EINTR. It takes a few days until the newly version hits the test
> frameworks and we know for sure that is handled.
>
>> Couldn't follow where the issue was - kernel/userspace?
>    [ 10.397892] nvme_tcp: queue 0: failed to receive icresp, error -4
>
> Stable kernels started to return EINTR and one change which touches
> this area is:
>
>    578539e09690 ("nvme-tcp: fix connect failure on receiving partial ICResp PDU")
>
> Unfortunately, it's not easy for Luca to build a test kernel. If we
> provide one for his distro, he would be willing to tests.

Its not great that we now get sporadic EINTR errors. I am wandering what 
is triggering this?

Caleb, did you see this?



More information about the Linux-nvme mailing list