From: Stephen Hemminger <shemminger@vyatta.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Wang Chen <wangchen@cn.fujitsu.com>,
NETDEV <netdev@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: [PATCH] bridge: Check return of dev_set_promiscuity (v2)
Date: Fri, 20 Jun 2008 20:48:55 -0700 [thread overview]
Message-ID: <20080620204855.351c3cbb@extreme> (raw)
In-Reply-To: <485B16BB.1000604@cn.fujitsu.com>
Alternate version of Wang Chen's patch to handle dev_set_promiscuity
errors. I tried and make unwinds clearer here. The kobject_put can
just be replace by immediate kfree since object never gets registered
if going through that path.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
--- a/net/bridge/br_if.c 2008-06-20 15:57:51.000000000 -0700
+++ b/net/bridge/br_if.c 2008-06-20 16:15:47.000000000 -0700
@@ -373,10 +373,15 @@ int br_add_if(struct net_bridge *br, str
if (IS_ERR(p))
return PTR_ERR(p);
+ err = dev_set_promiscuity(dev, 1);
+ if (err)
+ goto err_free;
+
+
err = kobject_init_and_add(&p->kobj, &brport_ktype, &(dev->dev.kobj),
SYSFS_BRIDGE_PORT_ATTR);
if (err)
- goto err0;
+ goto err_unset_promiscuity;
err = br_fdb_insert(br, p, dev->dev_addr);
if (err)
@@ -388,7 +393,6 @@ int br_add_if(struct net_bridge *br, str
rcu_assign_pointer(dev->br_port, p);
dev_disable_lro(dev);
- dev_set_promiscuity(dev, 1);
list_add_rcu(&p->list, &br->port_list);
@@ -408,14 +412,17 @@ int br_add_if(struct net_bridge *br, str
kobject_uevent(&p->kobj, KOBJ_ADD);
return 0;
+
err2:
br_fdb_delete_by_port(br, p, 1);
err1:
kobject_del(&p->kobj);
goto put_back;
-err0:
- kobject_put(&p->kobj);
+err_unset_promiscuity:
+ dev_set_promiscuity(dev, -1);
+err_free:
+ kfree(p);
put_back:
dev_put(dev);
return err;
next prev parent reply other threads:[~2008-06-21 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:55 [PATCH net-next 3/8] bridge: Check return of dev_set_promiscuity Wang Chen
2008-06-20 1:18 ` Stephen Hemminger
2008-06-20 2:32 ` Wang Chen
2008-06-21 3:48 ` Stephen Hemminger [this message]
2008-06-21 5:45 ` [PATCH] bridge: Check return of dev_set_promiscuity (v3) Wang Chen
2008-06-20 2:08 ` [PATCH net-next 3/8] bridge: Check return of dev_set_promiscuity 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=20080620204855.351c3cbb@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=wangchen@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.