From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH net-next] net: vxlan: do not use vxlan_net before checking event type
Date: Fri, 17 Jan 2014 10:20:31 -0800 [thread overview]
Message-ID: <20140117102031.00002a33@unknown> (raw)
In-Reply-To: <1389959706-30976-1-git-send-email-dborkman@redhat.com>
On Fri, 17 Jan 2014 12:55:06 +0100
Daniel Borkmann <dborkman@redhat.com> wrote:
> Jesse Brandeburg reported that commit acaf4e70997f caused a panic
> when adding a network namespace while vxlan module was present in
> the system:
I ran a quick test and the namespace issue no longer occurs once this
patch is applied. As for this one vs Cong's, you guys can fight that
out. Thanks for fixing this.
Tested-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2014-01-17 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 11:55 [PATCH net-next] net: vxlan: do not use vxlan_net before checking event type Daniel Borkmann
2014-01-17 17:30 ` Cong Wang
2014-01-17 18:32 ` Daniel Borkmann
2014-01-18 3:50 ` Cong Wang
2014-01-18 17:18 ` Eric Dumazet
2014-01-18 17:57 ` Cong Wang
2014-01-18 19:47 ` Daniel Borkmann
2014-01-18 23:32 ` Cong Wang
2014-01-18 23:48 ` Cong Wang
2014-01-19 0:36 ` Daniel Borkmann
2014-01-19 0:50 ` Cong Wang
[not found] ` <1390072047.31367.543.camel@edumazet-glaptop2.roam.corp.google.com>
2014-01-18 23:38 ` Cong Wang
2014-01-19 2:01 ` Eric Dumazet
2014-01-17 18:20 ` Jesse Brandeburg [this message]
2014-01-18 2:50 ` David Miller
2014-01-20 21:51 ` Eric W. Biederman
2014-01-20 22:01 ` Daniel Borkmann
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=20140117102031.00002a33@unknown \
--to=jesse.brandeburg@intel.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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).