Red Hat Bugzilla – Bug 962187
vm down because of client reset. assert error
Last modified: 2015-06-02 11:34:48 EDT
Created attachment 746858 [details]
guest vm log
Description of problem:
Version-Release number of selected component (if applicable):
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:
guest vm assert.
guest should work as normal
i am not familar with the code, but i suggest there is a way on which each thread conmunicaate with each other
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.
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.
Removing needinfo on closed bugs.