nvme tcp receive errors

[Sagi Grimberg]

>> Thanks for the reply.
>>
>> This was observed on the recent 5.12-rc4, so it has all the latest tcp
>> fixes. I'll check with reverting 0dc9edaf80ea and see if that makes a
>> difference. It is currently reproducible, though it can take over an
>> hour right now.
> 
> After reverting 0dc9edaf80ea, we are observing a kernel panic (below).

Ah, that's probably because WRITE_ZEROS are not set with RQF_SPECIAL..
This patch is actually needed.


> We'll try adding it back, plust adding your debug patch.

Yes, that would give us more info about what is the state the
request is in when getting these errors