netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Miller <davem@davemloft.net>,
	Patrick McHardy <kaber@trash.net>,
	netdev@vger.kernel.org,
	Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [PATCH] veth: Cleanly handle a missing peer_tb argument on creation.
Date: Wed, 12 Sep 2007 18:15:02 +0400	[thread overview]
Message-ID: <46E7F466.1060704@openvz.org> (raw)
In-Reply-To: <m17imwaumb.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> I was getting strange kernel crashes when attempting to
> create veth devices when I did not specify a peer argument
> to /bin/ip.
> 
> So this patch defaults peer_tb to all zeros and doesn't attempt to
> reuse the netlink attributes for the primary link to create the
> secondary link and now I can't reproduce the failures.
> 
> Given that some of the most interesting netlink attributes to specify
> like a mac address or a network device name seem are generally
> the wrong thing to do this seems like the right approach.
> 
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> ---
>  drivers/net/veth.c |   16 +++++++---------
>  1 files changed, 7 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/net/veth.c b/drivers/net/veth.c
> index 9e6a746..d49bd2c 100644
> --- a/drivers/net/veth.c
> +++ b/drivers/net/veth.c
> @@ -313,7 +313,7 @@ static int veth_newlink(struct net_device *dev,
>  	struct net_device *peer;
>  	struct veth_priv *priv;
>  	char ifname[IFNAMSIZ];
> -	struct nlattr *peer_tb[IFLA_MAX + 1], **tbp;
> +	struct nlattr *peer_tb[IFLA_MAX + 1];
>  
>  	/*
>  	 * create and register peer first
> @@ -322,6 +322,7 @@ static int veth_newlink(struct net_device *dev,
>  	 * skip it since no info from it is useful yet
>  	 */
>  
> +	memset(peer_tb, 0, sizeof(peer_tb));
>  	if (data != NULL && data[VETH_INFO_PEER] != NULL) {
>  		struct nlattr *nla_peer;
>  
> @@ -336,21 +337,18 @@ static int veth_newlink(struct net_device *dev,
>  		err = veth_validate(peer_tb, NULL);
>  		if (err < 0)
>  			return err;
> +	}
>  
> -		tbp = peer_tb;
> -	} else
> -		tbp = tb;

The intention of this part was to get the same parameters for
peer as for the first device if no "peer" argument was specified
for ip utility. Does it still work?

> -
> -	if (tbp[IFLA_IFNAME])
> -		nla_strlcpy(ifname, tbp[IFLA_IFNAME], IFNAMSIZ);
> +	if (peer_tb[IFLA_IFNAME])
> +		nla_strlcpy(ifname, peer_tb[IFLA_IFNAME], IFNAMSIZ);
>  	else
>  		snprintf(ifname, IFNAMSIZ, DRV_NAME "%%d");
>  
> -	peer = rtnl_create_link(dev->nd_net, ifname, &veth_link_ops, tbp);
> +	peer = rtnl_create_link(dev->nd_net, ifname, &veth_link_ops, peer_tb);
>  	if (IS_ERR(peer))
>  		return PTR_ERR(peer);
>  
> -	if (tbp[IFLA_ADDRESS] == NULL)
> +	if (peer_tb[IFLA_ADDRESS] == NULL)
>  		random_ether_addr(peer->dev_addr);
>  
>  	err = register_netdevice(peer);


  parent reply	other threads:[~2007-09-12 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 13:19 [PATCH] veth: Cleanly handle a missing peer_tb argument on creation Eric W. Biederman
2007-09-12 13:31 ` David Miller
2007-09-12 14:15 ` Pavel Emelyanov [this message]
2007-09-12 14:48   ` Eric W. Biederman
2007-09-12 14:49     ` Pavel Emelyanov
2007-09-12 15:25       ` Eric W. Biederman
2007-09-13  6:06         ` Pavel Emelyanov
2007-09-13  9:02         ` Pavel Emelyanov

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=46E7F466.1060704@openvz.org \
    --to=xemul@openvz.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).