summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorJon Derrick <jonathan.derrick@intel.com>2017-07-12 10:58:19 -0600
committerChristoph Hellwig <hch@lst.de>2017-07-25 17:58:32 +0200
commit2fd4167fadd1360ab015e4f0e88e51843e49556c (patch)
tree09c31d75335c278aa1e946e59278412f8f7cc301 /include
parent6484f5d16f9d5368afac61091972242f3bd695a9 (diff)
nvme: fabrics commands should use the fctype field for data direction
Fabrics commands with opcode 0x7F use the fctype field to indicate data direction. Signed-off-by: Jon Derrick <jonathan.derrick@intel.com> Reviewed-by: Sagi Grimberg <sai@grmberg.me> Signed-off-by: Christoph Hellwig <hch@lst.de> Fixes: eb793e2c ("nvme.h: add NVMe over Fabrics definitions")
Diffstat (limited to 'include')
-rw-r--r--include/linux/nvme.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index bc74da018bdc..25d8225dbd04 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -1006,7 +1006,7 @@ static inline bool nvme_is_write(struct nvme_command *cmd)
* Why can't we simply have a Fabrics In and Fabrics out command?
*/
if (unlikely(cmd->common.opcode == nvme_fabrics_command))
- return cmd->fabrics.opcode & 1;
+ return cmd->fabrics.fctype & 1;
return cmd->common.opcode & 1;
}