Bug 962187
| Summary: | vm down because of client reset. assert error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | bigclouds <bigclouds> | ||||
| Component: | spice-server | Assignee: | Marc-Andre Lureau <marcandre.lureau> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.4 | CC: | bigclouds, cfergeau, dblechte, djasa, marcandre.lureau, mkenneth, mkrcmari, rbalakri | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | spice-server-0.12.4-10.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
No documentation needed
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1227410 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-10-14 05:04:30 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1227410 | ||||||
| Attachments: |
|
||||||
The spice-server rpm is old (rhel-6.3). Is this bug reproducible over Rhel6.4? If it is reproducible, can you please attach the qemu log file, running with the highest spice debug level (export SPICE_DEBUG_LEVEL=5, before executing qemu). This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Can you still reproduce this? snd_receive: ASSERT n failed It looks like a misbehaving client could easily reach that condition by sending too big messages. Instead of assert() we could replace with a warning. When a too big message is received, it would simply disconnect the channel. sent patch: http://lists.freedesktop.org/archives/spice-devel/2014-June/017015.html Hmm, from the log it seems you managed to get snd_channel_put: sound channel freed without a previous "snd_disconnect_channel: .." so the channel structure could also point to garbage. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1435.html Removing needinfo on closed bugs. |
Created attachment 746858 [details] guest vm log Description of problem: Version-Release number of selected component (if applicable): spice-server 0.10.*.rpm How reproducible: unplug cable, wait minutes(on purpose, sure server aware and clean infos of client) , plug cable again. repeat that process again and again(There is a probability). Steps to Reproduce: 1. 2. 3. Actual results: guest vm assert. Expected results: guest should work as normal Additional info: i am not familar with the code, but i suggest there is a way on which each thread conmunicaate with each other