target crash / host hang with nvme-all.3 branch of nvme-fabrics

Steve Wise swise at opengridcomputing.com
Tue Jun 28 12:43:03 PDT 2016


> I'm using a ram disk for the target.  Perhaps before
> I was using a real nvme device.  I'll try that too and see if I still hit this
> deadlock/stall...
> 

Hey Ming,

Seems using a real nvme device at the target vs a ram device, avoids this new
deadlock issue.  And I'm running so-far w/o the usual touch-after-free crash.
Usually I hit it quickly.   It looks like your patch did indeed fix that.  So:

1) We need to address Christoph's concern that your fix isn't the ideal/correct
solution.  How do you want to proceed on that angle?  How can I help?

2) the deadlock below is probably some other issue.  Looks more like a cxgb4
problem at first glance.  I'll look into this one...

Steve.





More information about the Linux-nvme mailing list