[CRIU] Crash during criu check (criu: mount_resolve_path(): criu killed by SIGSEGV)

[Adrian Reber]

On Wed, Oct 12, 2016 at 10:42:03AM -0700, Andrei Vagin wrote:
> On Mon, Oct 10, 2016 at 09:47:52AM +0200, Adrian Reber wrote:
> > On Fri, Oct 07, 2016 at 09:36:13AM +0300, Pavel Emelyanov wrote:
> > > On 10/04/2016 01:27 PM, Adrian Reber wrote:
> > > > I got a bug report against criu during criu ckeck:
> > > > 
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=1381351
> > > > 
> > > > The backtrace says:
> > > > 
> > > > #0  0x000000000045241d in mount_resolve_path (mntinfo_tree=<optimized out>, path=0xd2c340 "/var/lib/samba/private/msg.sock/937") at criu/mount.c:213
> > > > 213			list_for_each_entry(c, &m->children, siblings) {
> > > > 
> > > > https://bugzilla.redhat.com/attachment.cgi?id=1206963
> > > 
> > > Is there a way to reproduce this? I mean -- I there's a patch, would
> > > it be possible to quickly validate the guess is (was) right?
> > 
> > The bug happens every time also with 2.6. So yes, the reporter can try
> > patched versions.
> 
> Hi Adrian,
> 
> I tryed to analize this issue, but I think a whole core file and the
> criu binary with debuginfo are required. Can we get this information?

Not sure, but I would expect that it is possible. The easiest would
probably be if you directly ask in the bug report about it. More
effective than me acting as middle man.

		Adrian