From: "Vincent Stehlé" <vincent.stehle@intel.com>
To: linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Vincent Stehlé" <vincent.stehle@intel.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Christoph Hellwig" <hch@lst.de>
Subject: [PATCH] nvmet-rdma: Fix use after free
Date: Tue, 16 Aug 2016 15:11:25 +0200 [thread overview]
Message-ID: <1471353085-6743-1-git-send-email-vincent.stehle@intel.com> (raw)
In-Reply-To: <1470230393-23671-1-git-send-email-sagi@grimberg.me>
Avoid dereferencing the queue pointer in nvmet_rdma_release_queue_work()
after it has been freed by nvmet_rdma_free_queue().
Fixes: d8f7750a08968b10 ("nvmet-rdma: Correctly handle RDMA device hot removal")
Signed-off-by: Vincent Stehlé <vincent.stehle@intel.com>
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@lst.de>
---
drivers/nvme/target/rdma.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
index b4d6485..5de8d0a 100644
--- a/drivers/nvme/target/rdma.c
+++ b/drivers/nvme/target/rdma.c
@@ -978,10 +978,11 @@ static void nvmet_rdma_release_queue_work(struct work_struct *w)
container_of(w, struct nvmet_rdma_queue, release_work);
struct rdma_cm_id *cm_id = queue->cm_id;
struct nvmet_rdma_device *dev = queue->dev;
+ enum nvmet_rdma_queue_state state = queue->state;
nvmet_rdma_free_queue(queue);
- if (queue->state != NVMET_RDMA_IN_DEVICE_REMOVAL)
+ if (state != NVMET_RDMA_IN_DEVICE_REMOVAL)
rdma_destroy_id(cm_id);
kref_put(&dev->ref, nvmet_rdma_free_dev);
--
2.8.1
next prev parent reply other threads:[~2016-08-16 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 13:19 [PATCH v4] nvmet-rdma: Correctly handle RDMA device hot removal Sagi Grimberg
[not found] ` <1470230393-23671-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-08-04 11:50 ` Christoph Hellwig
2016-08-16 13:11 ` Vincent Stehlé [this message]
2016-08-16 13:17 ` [PATCH] nvmet-rdma: Fix use after free Sagi Grimberg
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=1471353085-6743-1-git-send-email-vincent.stehle@intel.com \
--to=vincent.stehle@intel.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.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