From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"quintela@redhat.com" <quintela@redhat.com>
Subject: Re: [PATCH] migration/rdma: Fix cm_event used before being initialized
Date: Mon, 17 May 2021 11:00:00 +0100 [thread overview]
Message-ID: <YKI+oJBc1ZT1AlC+@work-vm> (raw)
In-Reply-To: <1496057b-6a44-71a3-ca16-97c4d9e9650a@fujitsu.com>
* lizhijian@fujitsu.com (lizhijian@fujitsu.com) wrote:
>
>
> On 14/05/2021 01.15, Dr. David Alan Gilbert wrote:
> > * Li Zhijian (lizhijian@cn.fujitsu.com) wrote:
> >> A segmentation fault was triggered when i try to abort a postcopy + rdma
> >> migration.
> >>
> >> since rdma_ack_cm_event releases a uninitialized cm_event in thise case.
> >>
> >> like below:
> >> 2496 ret = rdma_get_cm_event(rdma->channel, &cm_event);
> >> 2497 if (ret) {
> >> 2498 perror("rdma_get_cm_event after rdma_connect");
> >> 2499 ERROR(errp, "connecting to destination!");
> >> 2500 rdma_ack_cm_event(cm_event); <<<< cause segmentation fault
> >> 2501 goto err_rdma_source_connect;
> >> 2502 }
> >>
> >> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> > OK, that's an easy fix then; but I wonder if we should perhaps remove
> > that rdma_ack_cm_event, if it's the get_cm_event that's failed?
>
> I also wondered, i checked the man page get_cm_event(3) which has not documented
>
> and checked some rdma examples, some of them try to ack it[1], but some not[2].
I think they're actually consistent:
> [1]: https://github.com/linux-rdma/rdma-core/blob/e381334c2915a5290565694947790d4aebaf2222/librdmacm/examples/mckey.c#L451
ret = rdma_get_cm_event(test.channel, &event);
if (!ret) {
ret = cma_handler(event->id, event);
rdma_ack_cm_event(event);
}
Note it's '!ret' - so it's only doing the ack if the get_cm_event
succeeded.
> [2]: https://github.com/linux-rdma/rdma-core/blob/e381334c2915a5290565694947790d4aebaf2222/librdmacm/examples/mckey.c#L342
ret = rdma_get_cm_event(test.channel, &event);
if (ret) {
perror("rdma_get_cm_event");
break;
}
that exits the loop (and skips the ack) in the (ret) - i.e.
only on error - no !
Dave
> Thanks
>
> >
> > Still,
> >
> >
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >
> >> ---
> >> migration/rdma.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/migration/rdma.c b/migration/rdma.c
> >> index 00eac34232..2dadb62aed 100644
> >> --- a/migration/rdma.c
> >> +++ b/migration/rdma.c
> >> @@ -2466,7 +2466,7 @@ static int qemu_rdma_connect(RDMAContext *rdma, Error **errp)
> >> .private_data = &cap,
> >> .private_data_len = sizeof(cap),
> >> };
> >> - struct rdma_cm_event *cm_event;
> >> + struct rdma_cm_event *cm_event = NULL;
> >> int ret;
> >>
> >> /*
> >> --
> >> 2.30.2
> >>
> >>
> >>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-05-17 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 11:37 [PATCH] migration/rdma: Fix cm_event used before being initialized Li Zhijian
2021-05-13 16:13 ` Philippe Mathieu-Daudé
2021-05-13 16:45 ` Philippe Mathieu-Daudé
2021-05-13 17:15 ` Dr. David Alan Gilbert
2021-05-14 1:29 ` lizhijian
2021-05-17 10:00 ` Dr. David Alan Gilbert [this message]
2021-05-19 6:40 ` lizhijian
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=YKI+oJBc1ZT1AlC+@work-vm \
--to=dgilbert@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).