summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorJames Smart <jsmart2021@gmail.com>2019-04-08 11:15:19 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-05-10 17:54:09 +0200
commit777943cd6c5f0b2c438e932a218d7c9fbeacd7a9 (patch)
tree8c70f5bea4e885e36032dfec52def59e556681aa /block
parent0e8e67b8147fbcdd2d858c5f4c82297e12565e3d (diff)
downloadlinux-stable-777943cd6c5f0b2c438e932a218d7c9fbeacd7a9.tar.gz
linux-stable-777943cd6c5f0b2c438e932a218d7c9fbeacd7a9.tar.bz2
linux-stable-777943cd6c5f0b2c438e932a218d7c9fbeacd7a9.zip
nvme-fc: correct csn initialization and increments on error
[ Upstream commit 67f471b6ed3b09033c4ac77ea03f92afdb1989fe ] This patch fixes a long-standing bug that initialized the FC-NVME cmnd iu CSN value to 1. Early FC-NVME specs had the connection starting with CSN=1. By the time the spec reached approval, the language had changed to state a connection should start with CSN=0. This patch corrects the initialization value for FC-NVME connections. Additionally, in reviewing the transport, the CSN value is assigned to the new IU early in the start routine. It's possible that a later dma map request may fail, causing the command to never be sent to the controller. Change the location of the assignment so that it is immediately prior to calling the lldd. Add a comment block to explain the impacts if the lldd were to additionally fail sending the command. Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com> Signed-off-by: James Smart <jsmart2021@gmail.com> Reviewed-by: Ewan D. Milne <emilne@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions