From mboxrd@z Thu Jan  1 00:00:00 1970
From: swise@opengridcomputing.com (Steve Wise)
Date: Tue, 28 Jun 2016 14:43:03 -0500
Subject: target crash / host hang with nvme-all.3 branch of nvme-fabrics
In-Reply-To: <022701d1d172$2743d990$75cb8cb0$@opengridcomputing.com>
References: <576306EE.4020306@grimberg.me>
 <01b901d1c80b$72f83680$58e8a380$@opengridcomputing.com>
 <CAF1ivSYUG4c7Ej-gNqA=aPFR2zkNq8KhBoodhp64wdY=eQLx6g@mail.gmail.com>
 <01c101d1c80d$96d13c80$c473b580$@opengridcomputing.com>
 <20160616203437.GA19079@lst.de>
 <01e701d1c810$91d851c0$b588f540$@opengridcomputing.com>
 <020201d1c812$ec94b430$c5be1c90$@opengridcomputing.com>
 <1467066582.7205.7.camel@ssi> <20160628091433.GA14149@lst.de>
 <005001d1d147$81cd8cb0$8568a610$@opengridcomputing.com>
 <20160628155159.GA3084@lst.de>
 <01dc01d1d15a$84f42670$8edc7350$@opengridcomputing.com>
 <1467132596.7205.11.camel@ssi>
 <022701d1d172$2743d990$75cb8cb0$@opengridcomputing.com>
Message-ID: <022901d1d175$48c899e0$da59cda0$@opengridcomputing.com>

> 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.