Re: [PATCH spice-gtk 1/9] channel: delay event report to after coroutine exit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 27, 2015 at 2:22 PM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote:
> My understanding was that before these changes, when
> g_coroutine_signal_emit was used to emit an error, this part of the code
> relied on c->state != SPICE_CHANNEL_STATE_RECONNECTING to avoid calling
> channel_connect(). Is this assertion now wrong after your changes?

What do you mean? now that signal is delayed after this check,
c->event might be != NONE. I wanted to be extra careful that it
doesn't attempt to reconnect when there is an error to be signaled.
However, reviewing the code, I think it is fine to add a check
instead:
    if (c->state == SPICE_CHANNEL_STATE_RECONNECTING) {
        g_warn_if_failed(c->event == SPICE_CHANNEL_NONE);

I'll change the patch to do that.


-- 
Marc-André Lureau
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]