From: Jesse Gross <jesse@nicira.com>
To: Thomas Glanzmann <thomas@glanzmann.de>,
Jesse Gross <jesse@nicira.com>,
"discuss@openvswitch.org" <discuss@openvswitch.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ovs-discuss] Linus GIT Head OOPs reproducable in open vswitch when running mininet topology
Date: Mon, 3 Feb 2014 18:48:31 -0800 [thread overview]
Message-ID: <CAEP_g=8Fr15BC8a910q3bXh8reeid6Bn3rKL91KPh2K8OwiwZA@mail.gmail.com> (raw)
In-Reply-To: <20140131181857.GA25034@glanzmann.de>
On Fri, Jan 31, 2014 at 10:18 AM, Thomas Glanzmann <thomas@glanzmann.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?
prev parent reply other threads:[~2014-02-04 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 20:44 Linus GIT Head OOPs reproducable in open vswitch when running mininet topology Thomas Glanzmann
2014-01-31 1:37 ` [ovs-discuss] " Jesse Gross
2014-01-31 2:33 ` Thomas Glanzmann
2014-01-31 18:07 ` Jesse Gross
2014-01-31 18:18 ` Thomas Glanzmann
2014-02-04 2:48 ` Jesse Gross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEP_g=8Fr15BC8a910q3bXh8reeid6Bn3rKL91KPh2K8OwiwZA@mail.gmail.com' \
--to=jesse@nicira.com \
--cc=discuss@openvswitch.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@glanzmann.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).