nvmet-fc: do not check for invalid target port in nvmet_fc_handle_fcp_rqst()
authorHannes Reinecke <hare@suse.de>
Tue, 25 May 2021 12:54:14 +0000 (14:54 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 14 Jul 2021 14:56:00 +0000 (16:56 +0200)
commit950a7399056dad9d40c7252811aa5b3df60f8d9c
treeb5ca4969e72e9a0602198bc4491e52d86e0882e4
parent66e8848482f2bfb742530e68852edada5114217f
nvmet-fc: do not check for invalid target port in nvmet_fc_handle_fcp_rqst()

[ Upstream commit 2a4a910aa4f0acc428dc8d10227c42e14ed21d10 ]

When parsing a request in nvmet_fc_handle_fcp_rqst() we should not
check for invalid target ports; if we do the command is aborted
from the fcp layer, causing the host to assume a transport error.
Rather we should still forward this request to the nvmet layer, which
will then correctly fail the command with an appropriate error status.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/nvme/target/fc.c