On Tue, May 01, 2018 at 03:41:56PM -0400, Nicolas Bouliane via discuss wrote: > Hi, > > We experienced a crash and we generated the backtrace from the core dump > with that command: gdb -se "ovs-vswitchd" -ex "bt full" -ex "thread apply > all bt" --batch -c /core > /tmp/backtrace.txt > > The file is in attachement. > > # ovs-vswitchd --version > ovs-vswitchd (Open vSwitch) 2.7.3 > > # cat /proc/version > Linux version 4.9.77-1-generic (root@c509c24b315f) (gcc version 7.2.0 (GCC) > ) #4+1516907002do~691dc34 SMP Thu Jan 25 19:04:34 UTC 2018 > > # lsmod | grep switch > openvswitch 139264 50 vport_stt > nf_nat_ipv6 16384 1 openvswitch > nf_nat_ipv4 16384 2 openvswitch,iptable_nat > nf_nat 24576 3 openvswitch,nf_nat_ipv6,nf_nat_ipv4 > udp_tunnel 16384 1 openvswitch > nf_defrag_ipv6 36864 2 nf_conntrack_ipv6,openvswitch > nf_conntrack 110592 9 > nf_conntrack_ipv6,nf_conntrack_ftp,openvswitch,nf_conntrack_ipv4,nf_conntrack_netlink,xt_CT,nf_nat_ipv6,nf_nat_ipv4,nf_nat > libcrc32c 16384 2 openvswitch,raid456 > > Let me know if you need more information. We are curious to know if it is a > know bug, or if it is something new.
It's not obviously a known bug. It might be related to memory corruption, because SIGBUS can be caused by reading or writing a wild pointer and calloc(), which is at the top of the backtrace, can definitely do either one if there's been memory corruption. OVS 2.7.4 has a few memory corruption fixes, relative to OVS 2.7.3, so possibly it's a bug that's already fixed. Is this something that you see repeatedly? _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss