[CRIU] tty: No reg_d descriptor for id 0xe2

[Tycho Andersen]

On Mon, Jun 27, 2016 at 09:37:01AM -0600, Tycho Andersen wrote:
> On Mon, Jun 27, 2016 at 05:16:42PM +0200, Adrian Reber wrote:
> > On Mon, Jun 27, 2016 at 09:09:37AM -0600, Tycho Andersen wrote:
> > > On Mon, Jun 27, 2016 at 05:05:12PM +0200, Adrian Reber wrote:
> > > > On Mon, Jun 27, 2016 at 08:28:37AM -0600, Tycho Andersen wrote:
> > > > > I noticed I'm getting the error in the subject when c/r-ing containers
> > > > > which have been ssh'd into. Has anyone else seen this? Any ideas where
> > > > > to start looking?
> > > > 
> > > > I have no problems checkpointing a LXC container with a SSH session.
> > > > After the restore my SSH session keeps working without any problems.
> > > 
> > > Right, this is on restore. For me, the restore fails (i.e. criu
> > > exit(1)s). Does this not happen for you?
> > 
> > No, it works as always. lxc-2.0.0
> > 
> > The only line concerning reg_d in the log is:
> > 
> > (00.104549)    729: tty: Allocating fake descriptor for 0x83 (reg_d 0x7f60088d2450)
> 
> Ah, so yours actually works. Mine doesn't pass the is_pty() test and
> doesn't allocate a fake descriptor :(

Oh, I see, there is a typo :). I will send a patch shortly.

Tycho

> Tycho
> 
> > RHEL7 on the host and CentOS7 in the container.
> > 
> > 		Adrian
> 
>