nvme: fix handling of tls alerts

[Paul Moses]

> I guess I'm not surprised it was never merged. To answer another
> question: Was it ever reproduced? The answer is: I did not because I
> lacked NvME expertise to create such an enviroment that would trigger
> it. In NFS it was easily reproduced by modifying openssl to perform
> extra steps when establishing an NFS over TLS connection. Perhaps
> openssl could have been modified to do what's needed when NvME over
> TLS starts, but as I said I dont have the expertise. But the iter
> problem is the same for NFS as well as NvME so the problem is real.

On the nvme side, it used unmodified openssl 3.0 branch at commit 
068f2ff. It used the nvme command capsule to structure the data,
normal close_notify is used as payload to ensure the crash occurs 
100% of the time.

> I'm not attached to my patch and I would be happy for the issue to be
> resolved in whatever way is best suited.

How should I attribute your work? "Co-developed-by:"

Thanks,
Paul