[CRIU] [PATCHv2 0/9] Compatible (mostly) fixes

[Dmitry Safonov]

On 08/05/2016 04:47 AM, Andrew Vagin wrote:
> On Thu, Aug 04, 2016 at 09:48:55PM +0300, Cyrill Gorcunov wrote:
>> On Thu, Aug 04, 2016 at 06:07:40PM +0300, Dmitry Safonov wrote:
>>> v2: rebase on criu-dev with autofixed conflict by git
>>>
>>> There is three patches for issues I've found while was introducing
>>> CONFIG_COMPAT compile&make option, that do nothing with compat:
>>>   build/nmk: simplify try-cc and return true/false
>>>   make: drop check-build-packages - we can use try-cc now
>>>   make: propagate config DEFINES in CFLAGS
>>>
>>> For other patches: first four -- some fixes for compatible vdso
>>> on 3.X kernels (found while testing criu on vzkernel with compat
>>> patches set). Mostly -- there are different symbols in vdso for
>>> compat & native tasks, the sizes of vdso blob differ from native
>>> to compat and it's hard to make mremap() for vdso vma working --
>>> so use arch_prctl() API in the case when mremap() does not work.
>>>
>>> The last two patches in the set introduce CONFIG_COMPAT option
>>> which make gcc-multilib & glibc6-i686 *optional* dependencies
>>> for building CRIU.
>
> [root at fc24 criu]# python test/zdtm.py run -t zdtm/static/env00
> === Run 1/1 ================
>
> ========================== Run zdtm/static/env00 in h ==========================
> Start test
> ./env00 --pidfile=env00.pid --outfile=env00.out --envname=ENV_00_TEST
> Run criu dump
> Run criu restore
> =[log]=> dump/zdtm/static/env00/24/1/restore.log
> ------------------------ grep Error ------------------------
> (00.086424) Error (criu/cr-restore.c:1136): 24 killed by signal 11: Segmentation fault
> (00.086458) Error (criu/cr-restore.c:2018): Restoring FAILED.
> ------------------------ ERROR OVER ------------------------
> ################# Test zdtm/static/env00 FAIL at CRIU restore ##################
> ##################################### FAIL #####################################
>
> [root at fc24 criu]# tail test/dump/zdtm/static/env00/24/1/restore.log
> pie: 24: vdso: nbucket 0x3 nchain 0xb bucket 0x7fff77544128 chain 0x7f>
> pie: 24: ff77544134
> pie: 24: vdso: image [vdso] 0x7fff77544000-0x7fff77546000 [vvar] 0x7ff>
> pie: 24: f77541000-0x7fff77544000
> pie: 24: vdso: Runtime vdso/vvar matches dumpee, remap inplace
> pie: 24: vdso: Remap dumpee 0x26000 -> 0x7fff77541000
> pie: 24: vdso: Remap dumpee 0x29000 -> 0x7fff77544000
> pie: 24: Restoring scheduler params 0.0.0
> (00.086424) Error (criu/cr-restore.c:1136): 24 killed by signal 11: Segmentation fault
> (00.086458) Error (criu/cr-restore.c:2018): Restoring FAILED.

Hmm, It's on Jenkins, right?
I'll fix this -- if you could tell which patch introduces this, it would
help.

Thanks,
              Dmitry