public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@nvidia.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	Roopa Prabhu <roopa@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Ido Schimmel <idosch@nvidia.com>,
	Rafael Richter <rafael.richter@gin.de>,
	Daniel Klauer <daniel.klauer@gin.de>,
	Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH v2 net-next 1/8] net: bridge: vlan: notify switchdev only when something changed
Date: Tue, 15 Feb 2022 12:12:11 +0200	[thread overview]
Message-ID: <a38ac2a6-d9b9-190a-f144-496be1768b98@nvidia.com> (raw)
In-Reply-To: <20220215095405.d2cy6rjd2faj3az2@skbuf>

On 15/02/2022 11:54, Vladimir Oltean wrote:
> On Tue, Feb 15, 2022 at 10:54:26AM +0200, Nikolay Aleksandrov wrote:
>>> +/* return true if anything will change as a result of __vlan_add_flags,
>>> + * false otherwise
>>> + */
>>> +static bool __vlan_flags_would_change(struct net_bridge_vlan *v, u16 flags)
>>> +{
>>> +	struct net_bridge_vlan_group *vg;
>>> +	u16 old_flags = v->flags;
>>> +	bool pvid_changed;
>>>  
>>> -	return ret || !!(old_flags ^ v->flags);
>>> +	if (br_vlan_is_master(v))
>>> +		vg = br_vlan_group(v->br);
>>> +	else
>>> +		vg = nbp_vlan_group(v->port);
>>> +
>>> +	if (flags & BRIDGE_VLAN_INFO_PVID)
>>> +		pvid_changed = (vg->pvid == v->vid);
>>> +	else
>>> +		pvid_changed = (vg->pvid != v->vid);
>>> +
>>> +	return pvid_changed || !!(old_flags ^ v->flags);
>>>  }
>>
>> These two have to depend on each other, otherwise it's error-prone and
>> surely in the future someone will forget to update both.
>> How about add a "commit" argument to __vlan_add_flags and possibly rename
>> it to __vlan_update_flags, then add 2 small helpers like __vlan_update_flags_precommit
>> with commit == false and __vlan_update_flags_commit with commit == true.
>> Or some other naming, the point is to always use the same flow and checks
>> when updating the flags to make sure people don't forget.
> 
> You want to squash __vlan_flags_would_change() and __vlan_add_flags()
> into a single function? But "would_change" returns bool, and "add"
> returns void.
> 

Hence the wrappers for commit == false and commit == true. You could name the precommit
one __vlan_flags_would_change or something more appropriate. The point is to make
sure we always update both when flags are changed.

>>>  
>>>  static int __vlan_vid_add(struct net_device *dev, struct net_bridge *br,
>>> @@ -672,9 +685,13 @@ static int br_vlan_add_existing(struct net_bridge *br,
>>>  {
>>>  	int err;
>>>  
>>> -	err = br_switchdev_port_vlan_add(br->dev, vlan->vid, flags, extack);
>>> -	if (err && err != -EOPNOTSUPP)
>>> -		return err;
>>> +	*changed = __vlan_flags_would_change(vlan, flags);
>>> +	if (*changed) {
>>> +		err = br_switchdev_port_vlan_add(br->dev, vlan->vid, flags,
>>> +						 extack);
>>> +		if (err && err != -EOPNOTSUPP)
>>> +			return err;
>>> +	}
>>
>> You should revert *changed to false in the error path below,
>> otherwise we will emit a notification without anything changed
>> if the br_vlan_is_brentry(vlan)) { } block errors out.
> 
> Ok.


  parent reply	other threads:[~2022-02-15 10:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 23:31 [PATCH v2 net-next 0/8] Replay and offload host VLAN entries in DSA Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 1/8] net: bridge: vlan: notify switchdev only when something changed Vladimir Oltean
2022-02-15  0:05   ` Vladimir Oltean
2022-02-15  8:54   ` Nikolay Aleksandrov
2022-02-15  9:54     ` Vladimir Oltean
2022-02-15 10:10       ` Vladimir Oltean
2022-02-15 10:15         ` Nikolay Aleksandrov
2022-02-15 10:12       ` Nikolay Aleksandrov [this message]
2022-02-15 10:30         ` Vladimir Oltean
2022-02-15 11:08           ` Nikolay Aleksandrov
2022-02-15 11:10             ` Nikolay Aleksandrov
2022-02-15 14:36             ` Vladimir Oltean
2022-02-15 15:38             ` Vladimir Oltean
2022-02-15 15:44               ` Nikolay Aleksandrov
2022-02-15 15:52                 ` Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 2/8] net: bridge: switchdev: differentiate new VLANs from changed ones Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 3/8] net: bridge: make nbp_switchdev_unsync_objs() follow reverse order of sync() Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 4/8] net: bridge: switchdev: replay all VLAN groups Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 5/8] net: switchdev: rename switchdev_lower_dev_find to switchdev_lower_dev_find_rcu Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 6/8] net: switchdev: introduce switchdev_handle_port_obj_{add,del} for foreign interfaces Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 7/8] net: dsa: add explicit support for host bridge VLANs Vladimir Oltean
2022-02-14 23:31 ` [PATCH v2 net-next 8/8] net: dsa: offload bridge port VLANs on foreign interfaces Vladimir Oltean

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=a38ac2a6-d9b9-190a-f144-496be1768b98@nvidia.com \
    --to=nikolay@nvidia.com \
    --cc=andrew@lunn.ch \
    --cc=daniel.klauer@gin.de \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=rafael.richter@gin.de \
    --cc=roopa@nvidia.com \
    --cc=tobias@waldekranz.com \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.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