Bug 1290884

Summary:	migration/RDMA: Race condition in sending control messages
Product:	Red Hat Enterprise Linux 8	Reporter:	Dr. David Alan Gilbert <dgilbert>
Component:	qemu-kvm	Assignee:	Dr. David Alan Gilbert <dgilbert>
qemu-kvm sub component:	Live Migration	QA Contact:	Li Xiaohui <xiaohli>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	chayang, jinzhao, juzhang, pezhang, qzhang, rbalakri, virt-maint, xfu
Version:	---
Target Milestone:	pre-dev-freeze
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-01 03:02:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dr. David Alan Gilbert 2015-12-11 19:01:55 UTC

Description of problem:
There's a race in qemu_rdma_post_send_control, where the reply from the destination might arrive before the signalled ack sending the 'ready'; when this happens wait_for_wrid loses the reply from the destination because it's only interested in waiting for the ack.

Version-Release number of selected component (if applicable):
still in 7.2 and upstream 2.5

How reproducible:
Only reproduced in my world where I'm sending a heck of a lot more control data, but I think it's a valid race

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Ademar Reis 2020-02-05 22:42:34 UTC

QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 7 RHEL Program Management 2020-11-01 03:02:51 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 Red Hat Bugzilla 2023-09-14 03:14:41 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days