| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAEP_g=8Fr15BC8a910q3bXh8reeid6Bn3rKL91KPh2K8OwiwZA@mail.gmail.com> Date: Mon, 3 Feb 2014 18:48:31 -0800 From: Jesse Gross <jesse@...ira.com> To: Thomas Glanzmann <thomas@...nzmann.de>, Jesse Gross <jesse@...ira.com>, "discuss@...nvswitch.org" <discuss@...nvswitch.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology On Fri, Jan 31, 2014 at 10:18 AM, Thomas Glanzmann <thomas@...nzmann.de> wrote: >> Do you know if this happens with an older kernel or with a simpler topology? > > No, I don't. I just verified that the Ubuntu Mininet uses the > openvswitch kernel module from openvswitch and not the one that is > shipped with the kernel. Ubuntu precise does not crash with the exact same > topology. The kernel from Precise doesn't call the function that is triggering the problem, so it's not too surprising that it doesn't have the same issue. It's not clear that this is actually a bug in the OVS code since it happens in a different function and that function accesses data that OVS doesn't really touch. Do you know if this happens with the bridge? Or can you try bisecting? Or use gdb to track down the faulting address? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists