[CRIU] dump failed on sk-tcp.c:231

Ying Han yinghan at google.com
Wed Oct 30 14:41:41 PDT 2013


On Wed, Oct 30, 2013 at 12:00 PM, Andrey Wagin <avagin at gmail.com> wrote:

> 2013/10/30 Ying Han <yinghan at google.com>:
> > Hi:
> >
> > This dump failure is triggered by running v3.9 + criu v0.5 with rpc
> > benchmark. It is not happening each time but quite often. Also similar
> issue
> > has been noticed on criu head few weeks back as well.
>
> This bug may be fixed by the following commits.
>
> commit 522fa17071710f16c4a49b6e4aa1687a9cda48ba
> Author: Andrey Vagin <avagin at openvz.org>
> Date:   Tue Sep 17 23:55:08 2013 +0400
>
>     iptables: use OUTPUT table to block locally-generated packet
>
> commit 0a1b70bb23d46f6bcd86bcafabcb4b99e03760a7
> Author: Andrew Vagin <avagin at openvz.org>
> Date:   Tue Aug 6 14:21:12 2013 +0400
>
>     tcp: block connections in both directions
>
> In addition the kernel v3.9 doesn't have a few fixes for tcp:
>
> linux-cr: 2cafdead tcp: don't apply tsoffset if rcv_tsecr is zero v3.11
> merged
> linux-cr: 85f70a00 tcp: initialize rcv_tstamp for restored sockets v3.11
> merged
> linux-cr: 81841048 tcp: set timestamps for restored skb-s v3.11 merged
>
>
Thanks Andrey for the pointers and we would patch the kernel as well as
criu to give a try.

--Ying

> Thanks,
> Andrey
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131030/15649806/attachment.html>


More information about the CRIU mailing list