<div dir="ltr"><div>Kernel version is 3.16, criu 1.6&1.7, libc 2.19, gcc 4.8.3.<br>I asked in the start email about kernel options bz for criu 1.7 check has failed.<br><span class="im">> > > Result of criu check --ms for criu 1.7(4c5b23e52c1dc4e3fbbc7472b92e7b1ce9d22f02):<br>
> > ><br>
> > > Warn (cr-check.c:189): Skipping unssuported PR_SET_MM_MAP<br>
> > ><br>
> > > Warn (cr-check.c:588): Skipping PTRACE_O_SUSPEND_SECCOMP check<br>
> > ><br>
> > > Warn (cr-check.c:615): Dirty tracking is OFF. Memory snapshot will not work.<br>
> > ><br>
> > > Error (timerfd.c:55): timerfd: No timerfd support for c/r: Inappropriate ioctl for device<br>
> > ><br>
> > > Warn (cr-check.c:702): Skipping unsupported AIO remap<br>
> > ><br>
> > > Warn (cr-check.c:718): fdinfo doesn't contain the lock field</span><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-11-02 19:32 GMT+03:00 Christopher Covington <span dir="ltr"><<a href="mailto:cov@codeaurora.org" target="_blank">cov@codeaurora.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 11/02/2015 10:59 AM, Pavel Emelyanov wrote:<br>
> On 10/30/2015 05:48 PM, Artem Kuzmitskiy wrote:<br>
>><br>
>><br>
>> 2015-10-30 16:33 GMT+03:00 Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>>:<br>
>><br>
>> On 10/30/2015 04:17 PM, Artem Kuzmitskiy wrote:<br>
>> ><br>
>> ><br>
>> > 2015-10-30 12:52 GMT+03:00 Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>>>:<br>
>> ><br>
>> > On 10/30/2015 12:38 PM, Artem Kuzmitskiy wrote:<br>
>> > > Hi all,<br>
>> > ><br>
>> > > I checked criu on armv7 with 3.16 kernel and got next error when restoring:<br>
>> > > ....<br>
>> > > (00.087176) 6034: task_args: 0xd6000<br>
>> > > task_args->pid: 6034<br>
>> > > task_args->nr_threads: 1<br>
>> > > task_args->clone_restore_fn: 0xd1c90<br>
>> > > task_args->thread_args: 0xd62c0<br>
>> > > pie: Switched to the restorer 6034<br>
>> > > pie: Error (pie/restorer.c:772): Unable to unmap (-): 1992687616<br>
>> ><br>
>> > Ouch, the pie logging is ... not complete :) Can you strace the restoring<br>
>> > to see what's going on with this syscall?<br>
>> ><br>
>> ><br>
>> > Strace log (command -strace criu restore -d -D images -o restore.log -v4 --shell-job -t 11758)<br>
>><br>
>> Plz, add -f option to strace, the subtasks syscalls are of the main interest.<br>
><br>
> I see no failed munmap-s in the strace below. And this part<br>
><br>
>> clone(Process 4820 attached<br>
>> child_stack=0x7e894b00, flags=SIGCHLD) = 4820<br>
>> [pid 5387] gettimeofday({1446215777, 101923}, NULL) = 0<br>
>> [pid 5387] write(1023, "(00.031539) PID: real 4820 virt "..., 37) = 37<br>
>> [pid 5387] flock(3, LOCK_UN) = 0<br>
>> [pid 5387] close(3) = 0<br>
>> [pid 5387] gettimeofday({1446215777, 103520}, NULL) = 0<br>
>> [pid 5387] write(1023, "(00.033136) Wait until namespace"..., 46) = 46<br>
>> [pid 5387] futex(0x76f7a010, FUTEX_WAIT, 1, NULL<br>
<br>
>> syscall: unknown syscall trap 0x0f000000<br>
<br>
</div></div>I overlooked this before. Is that a syscall number? What syscall is that<br>
supposed to be? Could there be a criu vs kernel or libc vs kernel feature<br>
mismatch?<br>
<div class="HOEnZb"><div class="h5"><br>
Christopher Covington<br>
<br>
--<br>
Qualcomm Innovation Center, Inc.<br>
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,<br>
a Linux Foundation Collaborative Project<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Best regards,<div>Artem Kuzmitskiy</div><div><br></div></div></div></div></div>
</div>