[CRIU] Name resolved on unconnected socket

[Cyrill Gorcunov]

On Mon, Feb 24, 2014 at 01:38:34PM +0100, Inti Gonzalez-Herrera wrote:
>    Hi,
> 
>    I am enclosing the output you asked me. Also, I tested the hypothesis
>    about CLOSE_WAIT with two programs and it fail with the same message.
>    Nevertheless, looking to the output you asked me I see  the error is on
>    socket d9de (55774).
> 
>    I executed lsof and I found this line
>    java      4178   root    8u  IPv6  55774      0t0  TCP
>    argos.irisa.fr:33329->isis.entimid.org:http (CLOSE_WAIT).
> 
>    So, for me the problem is with CLOSE_WAIT. I was reading some information
>    regarding this state and I am wondering if you avoid dumping because the
>    process may be waiting some messages. Anyway, shouldn't CRIU close the
>    connection anyway??? Maybe it is not a good idea in the general case, but
>    it is a good idea to provide a flag for doing so. In my case, it seems
>    that Java is not closing the connection until the collector is call it.
>    Anyway, I am not sure since I don't have the source code of the
>    middleware.

Well, as far as I know, yes. close-wait is not the state we can safely
ignore. On the other hands restoring such socket in closed state is
not hard. Pavel?

P.S. Please don't drop criu mailing list from email thread.