[lxc-users] Seg fault when using VLAN mode network

[Rory McCann]

Serge Hallyn <serge.hallyn at ...> writes:
> 
> Quoting Serge Hallyn (serge.hallyn <at> ubuntu.com):
> > Quoting Rory McCann (Rory.McCann <at> riverbed.com):
> ..
> > > Now, after exiting the container and re-running the lxc-execute
command, I straightaway get a
> segmentation fault, and the following kernel stacktrace:
> > > 
> > > [  169.728142] ------------[ cut here ]------------
> > > [  169.728151] WARNING: CPU: 0 PID: 1382 at
/build/buildd/linux-3.13.0/fs/sysfs/dir.c:486 sysfs_warn_dup+0x86/0xa0()
> > > [  169.728153] sysfs: cannot create duplicate filename
'/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/net/eth1/upper_vlan10-0'
> > > [  169.728155] Modules linked in: 8021q garp mrp xt_CHECKSUM
iptable_mangle ipt_MASQUERADE
> iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat
nf_conntrack xt_tcpudp bridge stp
> llc iptable_filter ip_tables x_tables ppdev coretemp crct10dif_pclmul
crc32_pclmul
> ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw gf128mul
glue_helper ablk_helper
> cryptd serio_raw vmwgfx ttm drm vmw_vmci parport_pc i2c_piix4 shpchp lp
mac_hid parport psmouse
> vmxnet3 mptspi mptscsih mptbase floppy
> > > [  169.728204] CPU: 0 PID: 1382 Comm: lxc-execute Not tainted
3.13.0-32-generic #57-Ubuntu
> > 
> > I don't get this bug, and this appears to be a simple kernel bugl.  Does
> > eth1 exist?
> 
> Oh, wow.  I do get kernel lockups on a trusty box.  When I upgrade to
> the linux-image-generic-lts-utopic kernel, that goes away.  Can you
> try that?


Thanks, upgrading to that kernel seems to have fixed the issue.

(Sorry for the gmane-forwarded post - I forgot to subscribe before sending
my first mail.)