[PATCH v2] nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()

Chaitanya Kulkarni chaitanyak at nvidia.com
Tue Aug 30 00:35:31 PDT 2022


On 8/29/22 05:40, Maurizio Lombardi wrote:
> TCP_FIN_WAIT2 and TCP_LAST_ACK were not handled, the connection is closing
> so we can ignore them and avoid printing the "unhandled state"
> warning message.
> 
> [ 1298.852386] nvmet_tcp: queue 2 unhandled state 5
> [ 1298.879112] nvmet_tcp: queue 7 unhandled state 5
> [ 1298.884253] nvmet_tcp: queue 8 unhandled state 5
> [ 1298.889475] nvmet_tcp: queue 9 unhandled state 5
> 
> v2: Do not call nvmet_tcp_schedule_release_queue(), just ignore
> the fin_wait2 and last_ack states.
> 
> Signed-off-by: Maurizio Lombardi <mlombard at redhat.com>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch at nvidia.com>

-ck






More information about the Linux-nvme mailing list