nvme: fix handling of tls alerts

[Olga Kornievskaia]

On Mon, Apr 13, 2026 at 4:46 AM Hannes Reinecke <hare at suse.de> wrote:
>
> On 4/13/26 01:42, Chaitanya Kulkarni wrote:
> >    (+linux-nvme)
> >
>
> This should have been address by the patchset '[PATCH v2 0/4] address
> tls_alert_recv usage by NFS and NvME' from Olga.
> I _thought_ it had been merged already, but seems that it didn't.
> Olga?

I recall probing on the list about the patch but I couldn't get any
response. I lost track of it afterwards.

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.

I'm not attached to my patch and I would be happy for the issue to be
resolved in whatever way is best suited.
>
> Cheers,
>
> Hannes
> --
> Dr. Hannes Reinecke                  Kernel Storage Architect
> hare at suse.de                                +49 911 74053 688
> SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
> HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
>