[RFC v1 4/4] nvmet-discovery: do not use invalid port
Daniel Wagner
dwagner at suse.de
Tue Sep 5 03:40:24 PDT 2023
On Tue, Sep 05, 2023 at 08:50:32AM +0200, Christoph Hellwig wrote:
> > + /* No port assigned, portentrybinding is missing */
>
> Double new line above, and I think a missing white space before
> binding.
Yep, sorry.
> But I'm still confused how we can get here without req->port
> set. Can you try to do a little more analysis as I suspect we have
> a deeper problem somewhere.
I am only able to reproduce this if there are two connect/discovery
attempts happening at the same time. I'll collect some logs and attempt
to make some sense out of it.
More information about the Linux-nvme
mailing list