[CRIU] Name resolved on unconnected socket

[Inti Gonzalez-Herrera]

I am wondering:
Is it possible to write a plugin to handle such sockets? I mean, I know the
application won't use the sockets again, so I just want to discard them. My
question is: Will CRIU call the plugin list if it realizes that a socket
"has a name but is unconnected"??? Or in a different way: Will CRIU call
every single plugin before failing?

My idea of plugin is simple:
DUMP
1 - Verify that the object is the file descriptor for a TCP socket
2 - Verify that the socket is in CLOSE_WAIT state
3 - Report success without recording the object as saved

RESTORE (Maybe I don't need this one since I don't recorded nothing in DUMP)
1 - Ignore the object

What do you thing? Just note that it only make sense if I know that such
connections aren't waiting for nothing.




On 24 February 2014 13:54, Cyrill Gorcunov <gorcunov at gmail.com> wrote:

> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140224/3d169775/attachment.html>