netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC VLAN 10/10]: Use rtnl_link API
Date: Tue, 05 Jun 2007 14:31:59 -0700	[thread overview]
Message-ID: <4665D64F.4040601@candelatech.com> (raw)
In-Reply-To: <20070605143703.23717.96479.sendpatchset@localhost.localdomain>

Patrick McHardy wrote:
> [VLAN]: Use rtnl_link API
> 
> Signed-off-by: Patrick McHardy <kaber@trash.net>

> +static int vlan_newlink(struct net_device *dev,
> +			struct nlattr *tb[], struct nlattr *data[])
> +{
> +	struct vlan_dev_info *vlan = VLAN_DEV_INFO(dev);
> +	int err;
> +
> +	if (!tb[IFLA_LINK])
> +		return -EINVAL;
> +	if (!data[IFLA_VLAN_ID])
> +		return -EINVAL;
> +
> +	vlan->vlan_id  = nla_get_u16(data[IFLA_VLAN_ID]);
> +	vlan->real_dev = __dev_get_by_index(nla_get_u32(tb[IFLA_LINK]));

It seems you are scribbling on dev->priv before you validate that
it is OK to do so?

Or, maybe I'm just confused.

What is 'dev' here?

> +
> +	if (!vlan->real_dev)
> +		return -ENODEV;
> +	err = vlan_check_real_dev(vlan->real_dev, vlan->vlan_id);
> +	if (err < 0)
> +		return err;
> +
> +	err = vlan_changelink(dev, tb, data);
> +	if (err < 0)
> +		return err;
> +
> +	return register_vlan_dev(dev);
> +}


Other than this, this patch and the others in this series
look fine (except for the 4095 VID issue that we communicated
about earlier).

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2007-06-05 21:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 14:36 [RFC VLAN 00/10]: VLAN netlink support try 2 Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 01/10]: Fix off-by-ones in VLAN ID checks Patrick McHardy
2007-06-05 16:16   ` Ben Greear
2007-06-05 18:16     ` Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 02/10]: Convert name-based configuration functions to struct netdevice * Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 03/10]: Move some device intialization code to dev->init callback Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 04/10]: Move vlan_group allocation to seperate function Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 05/10]: Split up device checks Patrick McHardy
2007-06-05 14:36 ` [RFC VLAN 06/10]: Move device registation to seperate function Patrick McHardy
2007-06-05 14:37 ` [RFC VLAN 07/10]: Return proper error codes in register_vlan_device Patrick McHardy
2007-06-05 14:37 ` [RFC VLAN 08/10]: Use 32 bit value for skb->priority mapping Patrick McHardy
2007-06-05 14:37 ` [RFC VLAN 09/10]: Keep track of number of QoS mappings Patrick McHardy
2007-06-05 14:37 ` [RFC VLAN 10/10]: Use rtnl_link API Patrick McHardy
2007-06-05 21:31   ` Ben Greear [this message]
2007-06-05 21:58     ` Patrick McHardy
2007-06-05 22:03       ` Ben Greear
2007-06-05 16:25 ` [RFC VLAN 00/10]: VLAN netlink support try 2 Ben Greear
2007-06-05 18:28   ` Patrick McHardy
2007-06-05 20:08     ` Ben Greear
2007-06-05 21:12       ` Patrick McHardy

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=4665D64F.4040601@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    /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).