Thanks, Seth. Yes, I agree it might be the same issue as bug 1586997. My reproduce is complicated because we found the issue in our project development, so I tried to simulate the whole process to reproduce it.
I will report a bug again source package 'linux'. Thanks! Peng On Wed, Dec 21, 2016 at 10:21 PM, Seth Arnold <seth.arn...@canonical.com> wrote: > On Wed, Dec 21, 2016 at 09:52:11PM -0600, Peng Liu wrote: > > I found a kernel panic issue when I was using pipework to config the > > network of a docker container on an x86 board with all-snap image. The > > issue is related to the auditing module of Linux kernel. So it should be > an > > issue of pc-kernel-snap. > > Please file the bug against source package 'linux'. > > This looks vaguely related to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508737 > and: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997 > > (Your reproducer looks very different, taking a trip through AppArmor > first, but it looks to me like it's the kernel trying to audit unix domain > sockets that falls over, regardless of the path taken to get there.) > > But it's hard for me to confirm/deny this wild suspicion at this point. > > Thanks > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > >
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
