[PATCH] nvme-tcp: proper handling of tcp socket closing flows
Grupi, Elad
Elad.Grupi at dell.com
Sun Jan 31 10:47:22 EST 2021
Yes. That's looks good
-----Original Message-----
From: Sagi Grimberg <sagi at grimberg.me>
Sent: Saturday, 30 January 2021 0:10
To: Grupi, Elad; linux-nvme at lists.infradead.org
Subject: Re: [PATCH] nvme-tcp: proper handling of tcp socket closing flows
[EXTERNAL EMAIL]
> @@ -1453,9 +1453,27 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue)
> sock->sk->sk_state_change = nvmet_tcp_state_change;
> queue->write_space = sock->sk->sk_write_space;
> sock->sk->sk_write_space = nvmet_tcp_write_space;
> +
> + switch (sk->sk_state) {
> + case TCP_FIN_WAIT1:
> + case TCP_CLOSE_WAIT:
> + case TCP_CLOSE:
BTW, shouldn't this be if (sk->sk_state != TCP_ESTABLISHED) ?
More information about the Linux-nvme
mailing list