From: Potnuri Bharat Teja <bharat@chelsio.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>,
Dakshaja Uppalapati <dakshaja@chelsio.com>,
Christoph Hellwig <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvmet: fix dsm failure when payload does not match sgl descriptor
Date: Thu, 19 Mar 2020 22:53:40 +0530 [thread overview]
Message-ID: <20200319172339.GA29063@chelsio.com> (raw)
In-Reply-To: <20200124173942.2744-1-sagi@grimberg.me>
On Friday, January 01/24/20, 2020 at 23:09:42 +0530, Sagi Grimberg wrote:
> The host is allowed to pass the controller an sgl describing a buffer
> that is larger than the dsm payload itself, allow it when executing
> dsm.
>
> Reported-by: Dakshaja Uppalapati <dakshaja@chelsio.com>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
Hi Sagi,
I see this issue with 5.4 stable kernels. Can this be pushed to 5.4 stable?
Thanks.
> drivers/nvme/target/core.c | 12 ++++++++++++
> drivers/nvme/target/io-cmd-bdev.c | 2 +-
> drivers/nvme/target/io-cmd-file.c | 2 +-
> drivers/nvme/target/nvmet.h | 1 +
> 4 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
> index 28438b833c1b..9217c824620f 100644
> --- a/drivers/nvme/target/core.c
> +++ b/drivers/nvme/target/core.c
> @@ -938,6 +938,18 @@ bool nvmet_check_data_len(struct nvmet_req *req, size_t data_len)
> }
> EXPORT_SYMBOL_GPL(nvmet_check_data_len);
>
> +bool nvmet_check_data_len_lte(struct nvmet_req *req, size_t data_len)
> +{
> + if (unlikely(data_len > req->transfer_len)) {
> + req->error_loc = offsetof(struct nvme_common_command, dptr);
> + nvmet_req_complete(req, NVME_SC_SGL_INVALID_DATA | NVME_SC_DNR);
> + return false;
> + }
> +
> + return true;
> +}
> +EXPORT_SYMBOL_GPL(nvmet_check_data_len_lte);
> +
> int nvmet_req_alloc_sgl(struct nvmet_req *req)
> {
> struct pci_dev *p2p_dev = NULL;
> diff --git a/drivers/nvme/target/io-cmd-bdev.c b/drivers/nvme/target/io-cmd-bdev.c
> index b6fca0e421ef..ea0e596be15d 100644
> --- a/drivers/nvme/target/io-cmd-bdev.c
> +++ b/drivers/nvme/target/io-cmd-bdev.c
> @@ -280,7 +280,7 @@ static void nvmet_bdev_execute_discard(struct nvmet_req *req)
>
> static void nvmet_bdev_execute_dsm(struct nvmet_req *req)
> {
> - if (!nvmet_check_data_len(req, nvmet_dsm_len(req)))
> + if (!nvmet_check_data_len_lte(req, nvmet_dsm_len(req)))
> return;
>
> switch (le32_to_cpu(req->cmd->dsm.attributes)) {
> diff --git a/drivers/nvme/target/io-cmd-file.c b/drivers/nvme/target/io-cmd-file.c
> index caebfce06605..cd5670b83118 100644
> --- a/drivers/nvme/target/io-cmd-file.c
> +++ b/drivers/nvme/target/io-cmd-file.c
> @@ -336,7 +336,7 @@ static void nvmet_file_dsm_work(struct work_struct *w)
>
> static void nvmet_file_execute_dsm(struct nvmet_req *req)
> {
> - if (!nvmet_check_data_len(req, nvmet_dsm_len(req)))
> + if (!nvmet_check_data_len_lte(req, nvmet_dsm_len(req)))
> return;
> INIT_WORK(&req->f.work, nvmet_file_dsm_work);
> schedule_work(&req->f.work);
> diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h
> index 46df45e837c9..eda28b22a2c8 100644
> --- a/drivers/nvme/target/nvmet.h
> +++ b/drivers/nvme/target/nvmet.h
> @@ -374,6 +374,7 @@ bool nvmet_req_init(struct nvmet_req *req, struct nvmet_cq *cq,
> struct nvmet_sq *sq, const struct nvmet_fabrics_ops *ops);
> void nvmet_req_uninit(struct nvmet_req *req);
> bool nvmet_check_data_len(struct nvmet_req *req, size_t data_len);
> +bool nvmet_check_data_len_lte(struct nvmet_req *req, size_t data_len);
> void nvmet_req_complete(struct nvmet_req *req, u16 status);
> int nvmet_req_alloc_sgl(struct nvmet_req *req);
> void nvmet_req_free_sgl(struct nvmet_req *req);
> --
> 2.20.1
>
>
> _______________________________________________
> linux-nvme mailing list
> linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-19 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 17:39 [PATCH] nvmet: fix dsm failure when payload does not match sgl descriptor Sagi Grimberg
2020-01-24 18:28 ` Keith Busch
2020-01-24 18:35 ` Sagi Grimberg
2020-01-24 18:55 ` Keith Busch
2020-01-25 21:23 ` Christoph Hellwig
2020-01-27 7:23 ` Sagi Grimberg
2020-03-19 17:23 ` Potnuri Bharat Teja [this message]
2020-03-19 21:06 ` Sagi Grimberg
2020-03-20 5:48 ` Potnuri Bharat Teja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200319172339.GA29063@chelsio.com \
--to=bharat@chelsio.com \
--cc=dakshaja@chelsio.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).