netdev - Re: [PATCH] veth: delay peer link configuration after interfaces are tied

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <878tyr4zzc.fsf@zoro.exoscale.ch>
Date:	Mon, 30 May 2016 12:11:35 +0200
From:	Vincent Bernat <vincent@...nat.im>
To:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Vijay Pandurangan <vijayp@...ayp.ca>,
	Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] veth: delay peer link configuration after interfaces are tied

 ❦ 30 mai 2016 11:23 CEST, Nicolas Dichtel <nicolas.dichtel@...nd.com> :

>> @@ -466,6 +462,10 @@ static int veth_newlink(struct net *src_net, struct net_device *dev,
>>  
>>  	priv = netdev_priv(peer);
>>  	rcu_assign_pointer(priv->peer, dev);
>> +
>> +	err = rtnl_configure_link(peer, ifmp);
>> +	if (err < 0)
>> +		goto err_configure_peer;

> You should fix the error path. 'unregister_netdevice(dev)' is missing.

I am sending another patch to fix that. I am quite unsure if I do the
right thing here.
-- 
Don't stop with your first draft.
            - The Elements of Programming Style (Kernighan & Plauger)