[CRIU] [PATCH] test, pipes: Exhaustive test of shared pipes

Kirill Tkhai ktkhai at virtuozzo.com
Tue Dec 13 05:38:01 PST 2016


On 13.12.2016 15:33, Pavel Emelyanov wrote:
> OK, I've run myself. Patches pass this test, but fail the sent previously
> unix test.
> 
> I did it like this:
> 
> ./unix.py --depth 10 --sockets 3 --stream --keep
> 
> This test fails even on criu-dev, but failures are about lost socket name
> (which is bad, but not critical) and lost pending connection (which is very
> bad, we'll need to fix it).
> 
> With your patches applied the test additionally fails with 'cannot restore'
> reason, which is also very bad. E.g. this state dumps, but doesn't restore:
> 
> 	socket(S) = 1
> 	socket(S) = 2
> 	socket(S) = 3
> 	bind(1, $name-1)
> 	listen(1)
> 	connect(2, $name-1)
> 	bind(3, $name-3)
> 	listen(3)
> 
> In restore log:
> (00.022915)  26472: Error (criu/sk-unix.c:924): sk unix: Can't connect 0x79f4ee socket: Bad file descriptor

Yeah, it's error. I'll send v4 series to you.


More information about the CRIU mailing list