criu is not built for arm64

Bug #1709920 reported by dann frazier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
criu (Debian)
Fix Released
Unknown
criu (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Won't Fix
Undecided
Unassigned
Zesty
Won't Fix
Undecided
Unassigned

Bug Description

The criu package has source code for arch/aarch64, but arm64 is not listed in the control file so LP does not attempt to build it.

At least for artful, adding arm64 to the supported list in debian/control is sufficient for the build to succeed.

Tags: arm64
Raghuram Kota (rkota)
tags: added: arm64
Revision history for this message
dann frazier (dannf) wrote :

fyi, I tested the simple loop (https://criu.org/Simple_loop) on an artful system w/ a 4.12 kernel. While save & restore both exited w/ 0 status, the restored binary crashed:

[177195.809070] test.sh[35106]: unhandled level 2 translation fault (11) at 0xffffa0d826c0, esr 0x82000006
[177195.809074] pgd = ffff801f69cac000
[177195.812634] [ffffa0d826c0] *pgd=0000001f6b3aa003, *pud=0000001f4e855003, *pmd=0000000000000000
[177195.821452] CPU: 20 PID: 35106 Comm: test.sh Not tainted 4.12.0-10-generic #11-Ubuntu
[177195.821454] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012
[177195.821457] task: ffff801f46238000 task.stack: ffff801f65444000
[177195.821461] PC is at 0xffffa0d826c0
[177195.821464] LR is at 0xffffa0d826c0
[177195.821466] pc : [<0000ffffa0d826c0>] lr : [<0000ffffa0d826c0>] pstate: 60000000
[177195.821468] sp : 0000ffffc2ec3370
[177195.821470] x29: 0000ffffc2ec45c0 x28: 0000000123751000
[177195.821475] x27: 0000000123754b40 x26: 00000001529cc4b0
[177195.821480] x25: 0000ffffc2ec464c x24: 0000000000000000
[177195.821485] x23: 0000000123751000 x22: 0000000123751000
[177195.821490] x21: 0000000123751000 x20: 00000001529cc4b0
[177195.821495] x19: 0000000000000001 x18: 0000000123752000
[177195.821500] x17: 0000000123751000 x16: 0000000123751b10
[177195.821505] x15: 0000000000000000 x14: 0000000123751000
[177195.821510] x13: 0000000000000000 x12: 0000000123751000
[177195.821515] x11: 0000000000000000 x10: 0000000000000000
[177195.821520] x9 : 0000000000000000 x8 : 0000000000000104
[177195.821525] x7 : 0000000000000000 x6 : 0000000000000001
[177195.821530] x5 : 0000000123751000 x4 : 0000000000000000
[177195.821535] x3 : 0000000000000000 x2 : 0000000123754c70
[177195.821540] x1 : 00000001237523f0 x0 : 0000000000000011

Revision history for this message
Stéphane Graber (stgraber) wrote :

Hi,

CRIU does pretty frequent releases and Debian is keeping things very well in sync. So I'd recommend that the change be done in Debian, at which point we'll just sync criu from there.

Revision history for this message
Stéphane Graber (stgraber) wrote :

For Xenial, I'd suggest we wait for CRIU 3.4 to land in Artful which will get us s390x support too, then we can SRU that new CRIU to xenial under the hardware enablement exception as a newer CRIU is required for newer kernels.

Changed in criu (Debian):
status: Unknown → New
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Filed request to upgrade to v3.4 it works in my ppa...

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873002

Changed in criu (Debian):
status: New → Fix Released
Revision history for this message
Raghuram Kota (rkota) wrote :

@stgraber ; From comment #3, who's the right person/team to lead Xenial SRU, now that criu seems to have landed in Artful ? Thanks.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Is that patchset something that can actually be applied on the much much older CRIU we have in those releases? It doesn't really feel that way to me.

Also, please note that CRIU is in universe so that'd be a best effort/community work.

Changed in criu (Ubuntu):
status: New → Fix Released
Revision history for this message
David Britton (dpb) wrote :

This isn't something that's in plan right now.

Changed in criu (Ubuntu Xenial):
status: New → Won't Fix
Changed in criu (Ubuntu Zesty):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.