From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Fix error flow at nvme_rdma_configure_admin_queue()
Date: Fri, 15 Jun 2018 10:01:54 +0200 [thread overview]
Message-ID: <20180615080154.GA19525@lst.de> (raw)
In-Reply-To: <1528979864-3109-1-git-send-email-israelr@mellanox.com>
On Thu, Jun 14, 2018@12:37:44PM +0000, Israel Rukshin wrote:
> On error calling to nvme_rdma_free_queue() with admin queue
> frees the QE before it was allocated.
>
> Signed-off-by: Israel Rukshin <israelr at mellanox.com>
> Reviewed-by: Max Gurtovoy <maxg at mellanox.com>
This certainly matches what we do in nvme_rdma_free_queue, but it
looks like a little too much special casing vodoo to me.
The nvme_rdma_free_queue was added by Sagi last October to fix
a reconnect double free. But I wonder if we just need to move it
back instead and have a different double free protection. E.g.
in nvme_rdma_free_qe just check if qe->data is set first,
and the NULL it out when freeing.
next prev parent reply other threads:[~2018-06-15 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 12:37 [PATCH] nvme: Fix error flow at nvme_rdma_configure_admin_queue() Israel Rukshin
2018-06-15 8:01 ` Christoph Hellwig [this message]
2018-06-17 10:52 ` Max Gurtovoy
2018-06-19 5:41 ` Christoph Hellwig
2018-06-19 10:36 ` Sagi Grimberg
2018-06-19 12:09 ` Max Gurtovoy
2018-06-19 12:30 ` Sagi Grimberg
2018-06-19 16:08 ` Max Gurtovoy
2018-06-19 16:12 ` Sagi Grimberg
2018-06-19 16:21 ` Max Gurtovoy
2018-06-19 16:38 ` Sagi Grimberg
2018-06-19 11:57 ` Max Gurtovoy
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=20180615080154.GA19525@lst.de \
--to=hch@lst.de \
/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