nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
authorMaurizio Lombardi <mlombard@redhat.com>
Mon, 29 Aug 2022 12:40:30 +0000 (14:40 +0200)
committerChristoph Hellwig <hch@lst.de>
Wed, 31 Aug 2022 04:58:10 +0000 (07:58 +0300)
commit478814a5584197fa1fb18377653626e3416e7cd6
treeefaf903197c3da8917995066047ce0c45ebaf3f1
parentda0342a3aa0357795224e6283df86444e1117168
nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()

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@redhat.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/nvme/target/tcp.c