From: Jon Derrick <jonathan.derrick@intel.com>
Date: Wed, 12 Jul 2017 16:58:19 +0000 (-0600)
Subject: nvme: fabrics commands should use the fctype field for data direction
X-Git-Tag: v4.13-rc3~16^2~1^2~4
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2fd4167fadd1360ab015e4f0e88e51843e49556c;p=platform%2Fkernel%2Flinux-exynos.git

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")
---

diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index bc74da0..25d8225 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;
 }