Comment 0 for bug 1410852

Stopping a container and starting it again results in kernel stack trace with a vlan interface.

---8<---
lxc.network.type = vlan
lxc.network.flags = up
lxc.network.link = p3p1
lxc.network.vlan.id = 2
---8<---

dpkg -l | grep lxc
ii liblxc1 1.0.6-0ubuntu0.1 amd64 Linux Containers userspace tools (library)
ii lxc 1.0.6-0ubuntu0.1 amd64 Linux Containers userspace tools
ii lxc-templates 1.0.6-0ubuntu0.1 amd64 Linux Containers userspace tools (templates)
ii python3-lxc 1.0.6-0ubuntu0.1 amd64 Linux Containers userspace tools (Python 3.x bindings)

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=6d1fc9aa-735c-4e61-ae1c-0a9d2587e77b ro acpi_osi=Linux acpi=force acpi_enforce_resources=lax i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1

Snipplet from stack trace:
---8<---
[35188.374621] WARNING: CPU: 4 PID: 3933 at /build/buildd/linux-3.13.0/fs/sysfs/dir.c:486 sysfs_warn_dup+0x86/0xa0()
[35188.374623] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/net/p3p1/upper_vlan2'
---8<---

Is deconfiguration on stop of an lxc instance not working anymore?