From: Moshe Shemesh <moshe@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [RFC] rtnetlink: handle multiple vlan tags in set_vf_vlan
Date: Fri, 22 Feb 2019 04:58:06 +0000 [thread overview]
Message-ID: <24d8a96d-4bac-fe8d-1308-c2caee2a9d2c@mellanox.com> (raw)
In-Reply-To: <20190221175436.10767-1-sthemmin@microsoft.com>
On 2/21/2019 7:54 PM, Stephen Hemminger wrote:
> The netlink API for IFLA_VF_VLAN_LIST allows multiple VLAN tags to
> be passed (and the message was validated) but only the first VLAN
> tag was being passed to the device. Change to iterate over each tag received.
>
> Fixes: 79aab093a0b5 ("net: Update API for VF vlan protocol 802.1ad support")
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> net/core/rtnetlink.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index a51cab95ba64..3a9ec988ae21 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -2207,11 +2207,10 @@ static int do_setvfinfo(struct net_device *dev, struct nlattr **tb)
> if (tb[IFLA_VF_VLAN_LIST]) {
> struct ifla_vf_vlan_info *ivvl[MAX_VLAN_LIST_LEN];
> struct nlattr *attr;
> - int rem, len = 0;
> + int i, rem, len = 0;
>
> - err = -EOPNOTSUPP;
> if (!ops->ndo_set_vf_vlan)
> - return err;
> + return -EOPNOTSUPP;
>
> nla_for_each_nested(attr, tb[IFLA_VF_VLAN_LIST], rem) {
> if (nla_type(attr) != IFLA_VF_VLAN_INFO ||
> @@ -2224,13 +2223,15 @@ static int do_setvfinfo(struct net_device *dev, struct nlattr **tb)
>
> len++;
> }
> - if (len == 0)
> - return -EINVAL;
>
> - err = ops->ndo_set_vf_vlan(dev, ivvl[0]->vf, ivvl[0]->vlan,
> - ivvl[0]->qos, ivvl[0]->vlan_proto);
> - if (err < 0)
> - return err;
> + err = -EINVAL; /* empty list error */
> + for (i = 0; i < len; i++) {
> + err = ops->ndo_set_vf_vlan(dev, ivvl[i]->vf,
> + ivvl[i]->vlan, ivvl[i]->qos,
> + ivvl[i]->vlan_proto);
Doing that each vlan will just overwrite the vf vlan configuration set
by its preceding one.
Note #define MAX_VLAN_LIST_LEN 1
The point here was that I had to add the rtnl interface to set vf vlan
with option to set vf vlan protocol. While doing that I was asked to add
option to get a list of vlans from user to support QinQ, so once it will
be needed there won't be a need to add another rtnl interface.
The driver which will support setting double vlan or more per vf will
change MAX_VLAN_LIST_LEN and change the ndo function.
> + if (err < 0)
> + return err;
> + }
> }
>
> if (tb[IFLA_VF_TX_RATE]) {
>
next prev parent reply other threads:[~2019-02-22 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 17:54 [RFC] rtnetlink: handle multiple vlan tags in set_vf_vlan Stephen Hemminger
2019-02-21 18:34 ` Stefano Brivio
2019-02-21 18:52 ` Stephen Hemminger
2019-02-22 4:58 ` Moshe Shemesh [this message]
2019-02-22 18:09 ` Stephen Hemminger
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=24d8a96d-4bac-fe8d-1308-c2caee2a9d2c@mellanox.com \
--to=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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;
as well as URLs for NNTP newsgroup(s).