All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: yamahata@private.email.ne.jp, qemu-devel@nongnu.org, mrhines@us.ibm.com
Cc: quintela@redhat.com
Subject: [Qemu-devel] qemu_rdma_cleanup seg - related to 5a91337?
Date: Thu, 6 Feb 2014 12:26:12 +0000	[thread overview]
Message-ID: <20140206122611.GD3013@work-vm> (raw)

Hi Isaku,
   I hit a seg in qemu_rdma_cleanup in the code changed by your
'[PATCH] rdma: clean up of qemu_rdma_cleanup()'

migration-rdma.c ~ 2241

    if (rdma->qp) {
        rdma_destroy_qp(rdma->cm_id);
        rdma->qp = NULL;
    }

Your patch changed that to free cm_id at that point rather than
qp; but in my case cm_id is NULL and so rdma_destroy_qp segs.

given that there is a :

    if (rdma->cm_id) {
        rdma_destroy_id(rdma->cm_id);
        rdma->cm_id = NULL;
    }

later down, and there is now no longer any destroy of rdma->qp
I don't understand your change.

Your change text says:
  '- RDMAContext::qp is created by rdma_create_qp() so that it should be destroyed
   by rdma_destroy_qp(). not ibv_destroy_qp()'

but the diff is:
      if (rdma->qp) {
-        ibv_destroy_qp(rdma->qp);
+        rdma_destroy_qp(rdma->cm_id);
          rdma->qp = NULL;

should that have been rdma_destroy_qp(rdma->qp)?

Dave (who doesn't yet know enough RDMA to be dangerous)
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

             reply	other threads:[~2014-02-06 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 12:26 Dr. David Alan Gilbert [this message]
2014-02-17  7:28 ` [Qemu-devel] qemu_rdma_cleanup seg - related to 5a91337? Michael R. Hines
2014-02-17  9:06   ` Dr. David Alan Gilbert
2014-02-18  1:47     ` Michael R. Hines

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=20140206122611.GD3013@work-vm \
    --to=dgilbert@redhat.com \
    --cc=mrhines@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=yamahata@private.email.ne.jp \
    /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.