[CRIU] unexpected socket state dump failure

[Andrew Vagin]

On Thu, Oct 08, 2015 at 11:27:08PM +0000, Ross Boucher wrote:
> I'm now separately seeing this failure when checkpointing:
> 
> (00.163078) Error (sk-inet.c:211): Socket state 8 obtained but expected 7
Here are all states:

1        TCP_ESTABLISHED = 1,
2        TCP_SYN_SENT,  
3        TCP_SYN_RECV,
4        TCP_FIN_WAIT1,
5        TCP_FIN_WAIT2,
6        TCP_TIME_WAIT,
7        TCP_CLOSE,
8        TCP_CLOSE_WAIT,
9        TCP_LAST_ACK,
10       TCP_LISTEN,
11       TCP_CLOSING,    /* Now a valid state */
12        TCP_NEW_SYN_RECV,

criu supports only TCP_LISTEN, TCP_CLOSE, TCP_ESTABLISHED

I added TCP_CLOSE_WAIT, TCP_CLOSING, TCP_LAST_ACK, TCP_FIN_WAIT1,
TCP_FIN_WAIT2, but these patches were not committed.

> 
> 
> 
> On Thu, Oct 8, 2015 at 2:57 PM Ross Boucher <rboucher at gmail.com> wrote:
> 
> > Seems like the issue was that I was calling shutdown on a socket without
> > closing it.
> >
> > On Thu, Oct 8, 2015 at 2:25 PM Ross Boucher <rboucher at gmail.com> wrote:
> >
> >> Does anyone have an idea of what might cause this failure:
> >> (00.174924) Error (sk-inet.c:211): Socket state 4 obtained but expected 7
> >>
> >> -Ross
> >>
> >

> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu