[CRIU] Bad commit
Cyrill Gorcunov
gorcunov at gmail.com
Thu Aug 14 06:09:56 PDT 2014
On Thu, Aug 14, 2014 at 05:01:08PM +0400, Pavel Emelyanov wrote:
> On 08/14/2014 04:49 PM, Cyrill Gorcunov wrote:
> > On Thu, Aug 14, 2014 at 04:32:46PM +0400, Pavel Emelyanov wrote:
> >>> if ((clone_flags & CLONE_PARENT) &&
> >>> current->signal->flags & SIGNAL_UNKILLABLE)
> >>
> >> UNKILLABLE??? The caller of criu is unkillable?! Why?
> >
> > So, I'm restoring container with --restore-detached, where first process
> > is init with PID = 1, the kerne sets SIGNAL_UNKILLABLE to it, then new
> > fork continue using CLONE_PARENT and we exit out with error.
>
> That's the problem -- CLONE_PARENT is (should be) only set on criu -> init fork().
Yes, didn't find yet how this happen, reading criu code doesn't reveal this problem.
I'll ping once I find something new.
More information about the CRIU
mailing list