Sagi, suggest trying this patch.
The above reproduces with the patch applied on upstream nvme code.
Weird. I don't think the deadlock in your original report should
happen due to this. Can you take a look at the callstacks in the
reproduced deadlock? Either we're missing something obvious or it is a
a somewhat different deadlock.
The deadlock in this patchset reproduces upstream. It is not possible to
update the kernel in the env in the original report.
So IFF we assume that this does not reproduce in upstream (pending
proof), is there something that we can do with stable fixes? This will
probably go back to everything that is before 5.8...
