[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170530135420.51ff8617@griffin>
Date: Tue, 30 May 2017 13:54:20 +0200
From: Jiri Benc <jbenc@...hat.com>
To: Roopa Prabhu <roopa@...ulusnetworks.com>
Cc: Mark Bloch <markb@...lanox.com>,
"davem@...emloft.net" <davem@...emloft.net>,
pravin shelar <pshelar@....org>,
Alexander Duyck <aduyck@...antis.com>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Balki Raman <ramanb@...ulusnetworks.com>
Subject: Re: vxlan: use after free error
On Tue, 30 May 2017 13:47:55 +0200, Jiri Benc wrote:
> On Mon, 29 May 2017 11:37:22 -0700, Roopa Prabhu wrote:
> > This code is also hit via the OVS path, and i don't see a problem with
> > your changes and analysis but i am not too familiar with the ovs call
> > path. I see that the relevant developers are CC'ed.
>
> I don't see a problem with ovs and this patch. Ovs calls
> rtnl_delete_link.
>
> I'd prefer to have the code in a vxlan_vs_del_dev function to be
> symmetrical with vxlan_vs_add_dev similarly to what Roopa suggested. If
> you keep me in CC while resending I'll be happy to add my ack to the
> patch.
I replied to a wrong email in the thread but I guess it's obvious what
I wanted to reply to :-)
Sorry for that,
Jiri
Powered by blists - more mailing lists