[RESEND PATCH stable only] nvmet: set loop queue's segment boundary mask as PAGE_SIZE - 1
NVMe target only accepts single-page sg list, either file or block device backed target code follows this assumption.
However, loop target is one exception, given the sg list is from the host queue directly.
This patch sets loop queue's segment boundary mask as PAGE_SIZE - 1 for following NVMe target assumption.
Multi-page bvec has been merged to v5.1-rc1, so commit 02db99548d36 ("nvmet: fix building bvec from sg list") can fix the current issue simply without needing to limit the segment size for nvme-loop.
Reported-by: Yi Zhang yi.zhang@redhat.com Fixes: 3a85a5de29ea ("nvme-loop: add a NVMe loopback host driver") Cc: Yi Zhang yi.zhang@redhat.com Cc: Sagi Grimberg sagi@grimberg.me Cc: Chaitanya Kulkarni chaitanya.kulkarni@wdc.com Cc: stable@vger.kernel.org Signed-off-by: Ming Lei ming.lei@redhat.com --- drivers/nvme/target/loop.c | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/drivers/nvme/target/loop.c b/drivers/nvme/target/loop.c index b9f623ab01f3..7194f86b9dac 100644 --- a/drivers/nvme/target/loop.c +++ b/drivers/nvme/target/loop.c @@ -549,6 +549,9 @@ static int nvme_loop_create_io_queues(struct nvme_loop_ctrl *ctrl) if (ret) goto out_cleanup_connect_q;
+ /* target only accepts single-page sg list */ + blk_queue_segment_boundary(ctrl->ctrl.connect_q, PAGE_SIZE - 1); + return 0;
out_cleanup_connect_q:
On Tue, Apr 02, 2019 at 09:56:10AM +0800, Ming Lei wrote:
NVMe target only accepts single-page sg list, either file or block device backed target code follows this assumption.
However, loop target is one exception, given the sg list is from the host queue directly.
This patch sets loop queue's segment boundary mask as PAGE_SIZE - 1 for following NVMe target assumption.
Multi-page bvec has been merged to v5.1-rc1, so commit 02db99548d36 ("nvmet: fix building bvec from sg list") can fix the current issue simply without needing to limit the segment size for nvme-loop.
I don't understand, 02db99548d36 does not work for older kernels, so because of that, you need/want this patch to be applied? If so, what specific kernel versions do you want this to go to?
thanks,
greg k-h
On Wed, Apr 03, 2019 at 04:04:27PM +0200, Greg KH wrote:
On Tue, Apr 02, 2019 at 09:56:10AM +0800, Ming Lei wrote:
NVMe target only accepts single-page sg list, either file or block device backed target code follows this assumption.
However, loop target is one exception, given the sg list is from the host queue directly.
This patch sets loop queue's segment boundary mask as PAGE_SIZE - 1 for following NVMe target assumption.
Multi-page bvec has been merged to v5.1-rc1, so commit 02db99548d36 ("nvmet: fix building bvec from sg list") can fix the current issue simply without needing to limit the segment size for nvme-loop.
I don't understand, 02db99548d36 does not work for older kernels, so because of that, you need/want this patch to be applied? If so, what specific kernel versions do you want this to go to?
Old kernel needs both this patch and 02db99548d36, and you should see the description in 02db99548d36 commit log too.
This patch should be needed since nvme-loop is introduced.
Thanks, Ming
On Thu, Apr 04, 2019 at 12:22:27AM +0800, Ming Lei wrote:
On Wed, Apr 03, 2019 at 04:04:27PM +0200, Greg KH wrote:
On Tue, Apr 02, 2019 at 09:56:10AM +0800, Ming Lei wrote:
NVMe target only accepts single-page sg list, either file or block device backed target code follows this assumption.
However, loop target is one exception, given the sg list is from the host queue directly.
This patch sets loop queue's segment boundary mask as PAGE_SIZE - 1 for following NVMe target assumption.
Multi-page bvec has been merged to v5.1-rc1, so commit 02db99548d36 ("nvmet: fix building bvec from sg list") can fix the current issue simply without needing to limit the segment size for nvme-loop.
I don't understand, 02db99548d36 does not work for older kernels, so because of that, you need/want this patch to be applied? If so, what specific kernel versions do you want this to go to?
Old kernel needs both this patch and 02db99548d36, and you should see the description in 02db99548d36 commit log too.
This patch should be needed since nvme-loop is introduced.
I'm sorry, I still do not understand. Please resend the patches that you wish to have applied, with the proper git commit ids, and let us know what trees they should be applied to. I can not parse the above text, sorry.
greg k-h
linux-stable-mirror@lists.linaro.org
-
Greg KH -
Ming Lei