From: psajeepa@purestorage.com (Prabhath Sajeepa)
Subject: [PATCH] drivers/nvme/host/rdma.c: Fix double freeing of async event data
Date: Tue, 20 Nov 2018 13:11:13 -0700 [thread overview]
Message-ID: <1542744673-28129-1-git-send-email-psajeepa@purestorage.com> (raw)
Some error paths in configuration of admin queue free data buffer
associated with async request SQE without resetting the data buffer
pointer to NULL, This buffer is also freed up again if the controller
is shutdown or reset.
---
drivers/nvme/host/rdma.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
index d181caf..b61ae21 100644
--- a/drivers/nvme/host/rdma.c
+++ b/drivers/nvme/host/rdma.c
@@ -823,6 +823,7 @@ static int nvme_rdma_configure_admin_queue(struct nvme_rdma_ctrl *ctrl,
out_free_async_qe:
nvme_rdma_free_qe(ctrl->device->dev, &ctrl->async_event_sqe,
sizeof(struct nvme_command), DMA_TO_DEVICE);
+ ctrl->async_event_sqe.data = NULL;
out_free_queue:
nvme_rdma_free_queue(&ctrl->queues[0]);
return error;
--
2.7.4
next reply other threads:[~2018-11-20 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:11 Prabhath Sajeepa [this message]
2018-11-21 0:10 ` [PATCH] drivers/nvme/host/rdma.c: Fix double freeing of async event data Sagi Grimberg
2018-11-21 0:21 ` Roland Dreier
2018-11-21 0:30 ` Sagi Grimberg
[not found] ` <CAE=VkfB4G8PFZuNihQR0fei9BSr5ayqOrMWjFq9Xo5anQNgk7w@mail.gmail.com>
2018-11-21 1:57 ` Roland Dreier
[not found] ` <CAE=VkfBvD9gG3MuwptCdpZso3t0JsFTvO-s1q+aW9=Zm4QTR=Q@mail.gmail.com>
2018-11-21 4:37 ` Roland Dreier
2018-11-22 2:57 ` Sagi Grimberg
2018-11-26 17:17 Prabhath Sajeepa
2018-11-26 17:26 ` Roland Dreier
2018-11-27 7:33 ` Christoph Hellwig
2018-11-27 7:41 ` Sagi Grimberg
2018-11-27 7:42 ` Christoph Hellwig
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=1542744673-28129-1-git-send-email-psajeepa@purestorage.com \
--to=psajeepa@purestorage.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.