From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: dsa@cumulusnetworks.com, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org, mrv@mojatatu.com
Subject: Re: [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate
Date: Thu, 26 Oct 2017 00:49:11 +0300 [thread overview]
Message-ID: <43f36fb0-8543-7e60-a80e-6da35d74b69a@cumulusnetworks.com> (raw)
In-Reply-To: <1508848362-13750-1-git-send-email-nikolay@cumulusnetworks.com>
On 24/10/17 15:32, Nikolay Aleksandrov wrote:
> Hi,
> Before this set the bridge would generate a notification on vlan add or del
> even if they didn't actually do any changes, which confuses listeners and
> is generally not preferred. We could also lose notifications on actual
> changes if one adds a range of vlans and there's an error in the middle.
> The problem with just breaking and returning an error is that we could
> break existing user-space scripts which rely on the vlan delete to clear
> all existing entries in the specified range and ignore the non-existing
> errors (typically used to clear the current vlan config).
> So in order to make the notifications more accurate while keeping backwards
> compatibility we add a boolean that tracks if anything actually changed
> during the config calls.
>
> The vlan add is more difficult to fix because it always returns 0 even if
> nothing changed, but we cannot use a specific error because the drivers
> can return anything and we may mask it, also we'd need to update all places
> that directly return the add result, thus to signal that a vlan was created
> or updated and in order not to break overlapping vlan range add we pass
> down the new boolean that tracks changes to the add functions to check
> if anything was actually updated.
>
> Can't say that I am happy with this change, but currently I don't see any
> simpler way which doesn't affect user-space.
>
> v2: pass changed down to vlan add instead of masking errors
>
> Thanks,
> Nik
>
> Nikolay Aleksandrov (2):
> bridge: netlink: make setlink/dellink notifications more accurate
> bridge: vlan: signal if anything changed on vlan add
>
> net/bridge/br_netlink.c | 51 ++++++++++++++++-----------
> net/bridge/br_netlink_tunnel.c | 14 +++++---
> net/bridge/br_private.h | 6 ++--
> net/bridge/br_private_tunnel.h | 3 +-
> net/bridge/br_vlan.c | 78 ++++++++++++++++++++++++++++++------------
> 5 files changed, 102 insertions(+), 50 deletions(-)
>
Ah, forgot to update the non-vlan bridge config case with the empty stubs,
will send a fixed and tested v3 asap.
next prev parent reply other threads:[~2017-10-25 21:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 12:32 [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 20:51 ` kbuild test robot
2017-10-25 21:49 ` Nikolay Aleksandrov [this message]
2017-10-25 21:59 ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 21:59 ` [PATCH net-next v3 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-26 8:17 ` Stephen Hemminger
2017-10-26 8:25 ` Nikolay Aleksandrov
2017-10-25 21:59 ` [PATCH net-next v3 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 22:14 ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 " Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-25 22:52 ` [PATCH net-next v4 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-26 10:16 ` Toshiaki Makita
2017-10-26 11:02 ` [Bridge] " Nikolay Aleksandrov
2017-10-26 11:08 ` Nikolay Aleksandrov
2017-10-26 1:12 ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate David Miller
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=43f36fb0-8543-7e60-a80e-6da35d74b69a@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=dsa@cumulusnetworks.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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