> > > > 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? >
We don't see that repeatedly for now but I will keep an eye on it. If we start seeing it more, we might indeed upgrade to OVS 2.7.4. Thanks for you answer ! Cheers, Nicolas Bouliane Digital Ocean
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
