Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HV crash during running VMM related Hypercall fuzzing test. #2606

Closed
Mingyuan18 opened this issue Feb 25, 2019 · 2 comments
Closed

HV crash during running VMM related Hypercall fuzzing test. #2606

Mingyuan18 opened this issue Feb 25, 2019 · 2 comments
Assignees
Labels
priority: P2-High status: closed The issue been closed type: bug Something isn't working

Comments

@Mingyuan18
Copy link

Fuzzing test thread will call destroy_vm(IC_DESTROY_VM)
to set the guest vCPU state to VCPU_ZOMBIE then VCPU_INIT
and then VCPU_OFFLINE, it will cause post-work can't resume
the guest vCPU and can't changes the state of the
corresponding I/O request slot to REQ_STATE_FREE.

@Mingyuan18
Copy link
Author

[External_System_ID] ACRN-2234

@Mingyuan18 Mingyuan18 added type: bug Something isn't working status: new The issue status: new for creation status: Assigned Assigned priority: P2-High and removed status: new The issue status: new for creation labels Feb 25, 2019
wenlingz pushed a commit that referenced this issue Feb 26, 2019
This issue is triggered when launch fuzzing test.
Fuzzing test thread will call destroy_vm(IC_DESTROY_VM)
to set the guest vCPU state to VCPU_ZOMBIE then VCPU_INIT
and then VCPU_OFFLINE, it will cause post-work can't resume
the guest vCPU and can't changes the state of the
corresponding I/O request slot to REQ_STATE_FREE.

so replace improper use of ASSERT with return error code.

Tracked-On: #2606
Signed-off-by: Tianhua Sun <tianhuax.s.sun@intel.com>
Reviewed-by: Yonghua Huang <yonghua.huang@intel.com>
Acked-by: Eddie Dong <eddie.dong@intel.com>
@Mingyuan18
Copy link
Author

Patch has been merged, and issue cannot be reproduced,so close this issue.

@Mingyuan18 Mingyuan18 added status: closed The issue been closed and removed status: Assigned Assigned labels Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: P2-High status: closed The issue been closed type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants