public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
	"David S. Miller" <davem@davemloft.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next 3/4] net: dsa: mv88e6xxx: check hardware VLAN in use
Date: Sat, 13 Feb 2016 23:08:49 +0300	[thread overview]
Message-ID: <56BF8D51.5010108@cogentembedded.com> (raw)
In-Reply-To: <87mvr44cbh.fsf@ketchup.mtl.sfl>

On 02/13/2016 10:53 PM, Vivien Didelot wrote:

>>> The DSA drivers now have access to the VLAN prepare phase and the bridge
>>> net_device. It is easier to check for overlapping bridges from within
>>> the driver. Thus add such check in mv88e6xxx_port_vlan_prepare.
>>>
>>> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
>>> ---
>>>    drivers/net/dsa/mv88e6xxx.c | 64 +++++++++++++++++++++++++++++++++++++++++++++
>>>    1 file changed, 64 insertions(+)
>>>
>>> diff --git a/drivers/net/dsa/mv88e6xxx.c b/drivers/net/dsa/mv88e6xxx.c
>>> index 2e515e8..685dcb0 100644
>>> --- a/drivers/net/dsa/mv88e6xxx.c
>>> +++ b/drivers/net/dsa/mv88e6xxx.c
>>> @@ -1471,14 +1471,78 @@ static int _mv88e6xxx_vlan_init(struct dsa_switch *ds, u16 vid,
>>>    	return 0;
>>>    }
>>>
>>> +static int mv88e6xxx_port_check_hw_vlan(struct dsa_switch *ds, int port,
>>> +					u16 vid_begin, u16 vid_end)
>>> +{
>>> +	struct mv88e6xxx_priv_state *ps = ds_to_priv(ds);
>>> +	struct mv88e6xxx_vtu_stu_entry vlan;
>>> +	int i, err;
>>> +
>>> +	if (!vid_begin)
>>> +		return -EOPNOTSUPP;
>>> +
>>> +	mutex_lock(&ps->smi_mutex);
>>> +
>>> +	err = _mv88e6xxx_vtu_vid_write(ds, vid_begin - 1);
>>> +	if (err)
>>> +		goto unlock;
>>> +
>>> +	do {
>>> +		err = _mv88e6xxx_vtu_getnext(ds, &vlan);
>>> +		if (err)
>>> +			goto unlock;
>>
>>      Why are you not using *break*?
>
> I use goto for explicit error handling, and break for expected flow.

    Thought you'd say so. :-)
    I still think *break* is preferable...

>>> +
>>> +		if (!vlan.valid)
>>> +			break;
>>> +
>>> +		if (vlan.vid > vid_end)
>>> +			break;
>>> +
>>> +		for (i = 0; i < ps->num_ports; ++i) {
>>> +			if (dsa_is_dsa_port(ds, i) || dsa_is_cpu_port(ds, i))
>>> +				continue;
>>> +
>>> +			if (vlan.data[i] ==
>>> +			    GLOBAL_VTU_DATA_MEMBER_TAG_NON_MEMBER)
>>> +				continue;
>>> +
>>> +			if (ps->ports[i].bridge_dev ==
>>> +			    ps->ports[port].bridge_dev)
>>> +				break; /* same bridge, check next VLAN */
>>> +
>>> +			netdev_warn(ds->ports[port],
>>> +				    "hardware VLAN %d already used by %s\n",
>>> +				    vlan.vid,
>>> +				    netdev_name(ps->ports[i].bridge_dev));
>>> +			err = -EOPNOTSUPP;
>>> +			goto unlock;
>>> +		}
>>
>>      Why not *break*?
>
> Because here it would only break the for loop, and not the while loop.

    Oops, I overlooked the *for* loop. Sorry about that.

>>
>>> +	} while (vlan.vid < vid_end);
>>> +
>>> +unlock:
>>> +	mutex_unlock(&ps->smi_mutex);
>>> +
>>> +	return err;
>>> +}
>>> +
>> [...]
>
> Thanks,
> -v

MBR, Sergei

  reply	other threads:[~2016-02-13 20:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 17:09 [PATCH net-next 0/4] net: dsa: pass bridge device to drivers Vivien Didelot
2016-02-12 17:09 ` [PATCH net-next 1/4] net: dsa: mv88e6xxx: add port private structure Vivien Didelot
2016-02-12 17:09 ` [PATCH net-next 2/4] net: dsa: pass bridge down to drivers Vivien Didelot
2016-02-13 18:42   ` Florian Fainelli
2016-02-12 17:09 ` [PATCH net-next 3/4] net: dsa: mv88e6xxx: check hardware VLAN in use Vivien Didelot
2016-02-13 18:17   ` Sergei Shtylyov
2016-02-13 19:53     ` Vivien Didelot
2016-02-13 20:08       ` Sergei Shtylyov [this message]
2016-02-12 17:09 ` [PATCH net-next 4/4] net: dsa: remove dsa_bridge_check_vlan_range Vivien Didelot
2016-02-23 16:08 ` [PATCH net-next 0/4] net: dsa: pass bridge device to drivers Vivien Didelot
2016-02-23 19:53 ` 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=56BF8D51.5010108@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kernel@savoirfairelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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