Re: [Xen-devel] "xm save" trouble -- deadlock?

[Ewan Mellor <ewan@xxxxxxxxxxxxx>]

On Tue, Nov 01, 2005 at 06:15:27PM +0100, Gerd Knorr wrote:

> Some of the other threads behave in a strange way as well:
> 
>   master-xen root /vm/ttylinux# strace -p6568
>   Process 6568 attached - interrupt to quit
>   select(4, [3], [], [], {0, 960000})     = 0 (Timeout)
>   futex(0x80e53b8, FUTEX_WAKE, 1)         = 0
>   accept(3, 0x408193f8, [110])            = -1 EAGAIN (Resource 
> temporarily unavailable)
> 
> There is no point in calling accept(3) unless select() flags file handle 
> #3 as readable.

This mindboggling piece of loveliness is in xen/web/connection.py.  If you can
unpick it, a patch would be more than welcome!

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel