From: Stephen Hemminger <stephen@networkplumber.org>
To: Ido Schimmel <idosch@idosch.org>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
idosch@mellanox.com, netdev@vger.kernel.org, davem@davemloft.net,
bridge@lists.linux-foundation.org, mlxsw@mellanox.com,
peter@svinota.eu, cera@cera.cz
Subject: Re: [PATCH net] bridge: netlink: register netdevice before executing changelink
Date: Fri, 7 Apr 2017 14:45:13 -0400 [thread overview]
Message-ID: <20170407144513.086c3e9f@plumbers-lap.home.lan> (raw)
In-Reply-To: <20170407181649.GA21938@splinter>
On Fri, 7 Apr 2017 21:16:49 +0300
Ido Schimmel <idosch@idosch.org> wrote:
> On Fri, Apr 07, 2017 at 01:37:53PM -0400, Stephen Hemminger wrote:
> > Fix it right now. The patch you propose is too half baked.
>
> Given this patch needs to be back ported to three different stable
> kernels I tried to keep the amount of changes to a minimum while fixing
> the bug.
>
> I'll work on the ndo_uninit() patch and submit it. Then people can
> decide which course of action they're more comfortable with.
Other option for stable is to revert b6677449dff6 ("bridge: netlink: call br_changelink() during br_dev_newlink()")
prev parent reply other threads:[~2017-04-07 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 12:49 [PATCH net] bridge: netlink: register netdevice before executing changelink idosch
2017-04-07 14:10 ` Stephen Hemminger
2017-04-07 14:19 ` Nikolay Aleksandrov via Bridge
2017-04-07 15:22 ` Stephen Hemminger
2017-04-07 15:27 ` Nikolay Aleksandrov
2017-04-07 15:36 ` Stephen Hemminger
2017-04-07 15:43 ` Nikolay Aleksandrov via Bridge
2017-04-07 17:37 ` Stephen Hemminger
2017-04-07 18:16 ` Ido Schimmel
2017-04-07 18:44 ` Stephen Hemminger
2017-04-07 18:45 ` Stephen Hemminger [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=20170407144513.086c3e9f@plumbers-lap.home.lan \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=cera@cera.cz \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=peter@svinota.eu \
/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).