[Devel] protblem building criu on pcs7

Tycho Andersen tycho.andersen at canonical.com
Tue Nov 17 06:50:20 PST 2015


On Tue, Nov 17, 2015 at 05:12:56PM +0300, Cyrill Gorcunov wrote:
> Guys, recent changes in criu prevented me from continue building it
> on pcs7 kernel (ie on 3.10 higly lifted kernel) because there is
> no SECCOMP_SET_MODE_FILTER and SECCOMP_FILTER_FLAG_TSYNC constants
> defined in headers. That said for sure I can simply comment it out
> (or defined by my own), but such lack of constants means that we
> don't have this functionallity in kernel.
> 
> So what would be a safe strategy here: backport kernel patches,
> make this code compile-dependant or something else? Pavel?
> Asking simply because I'm not familiar with seccomp engine
> yet and cant provide a solution.

We should definitely define the constants in CRIU, it was just an
oversight that I didn't.

One other problem too is we'll have to make some change in
proc_parse.c as well, since it right now expects to parse Seccomp:
from /proc/self/status. I think the attached patch should work.

Tycho


More information about the Devel mailing list