From: Wang Chen <wangchen@cn.fujitsu.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "David S. Miller" <davem@davemloft.net>,
NETDEV <netdev@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH net-next 4/8] bridge: sysfs cleanup
Date: Sat, 21 Jun 2008 11:41:30 +0800 [thread overview]
Message-ID: <485C786A.8040204@cn.fujitsu.com> (raw)
In-Reply-To: <20080620104411.0fcff2e0@extreme>
Stephen Hemminger said the following on 2008-6-21 1:44:
> On Fri, 20 Jun 2008 08:55:15 +0800
> Wang Chen <wangchen@cn.fujitsu.com> wrote:
>
>> When I am doing this series of patch, I notice that bridge's sysfs are
>> not cleanuped after failure and bridge delete.
>>
>> Here is the patch for it.
>>
>> Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com>
>> ---
>> net/bridge/br_if.c | 2 ++
>> net/bridge/br_sysfs_if.c | 9 ++++++++-
>> 2 files changed, 10 insertions(+), 1 deletions(-)
>>
>> diff --git a/net/bridge/br_if.c b/net/bridge/br_if.c
>> index 49dd433..4b730fa 100644
>> --- a/net/bridge/br_if.c
>> +++ b/net/bridge/br_if.c
>> @@ -161,6 +161,7 @@ static void del_br(struct net_bridge *br)
>> struct net_bridge_port *p, *n;
>>
>> list_for_each_entry_safe(p, n, &br->port_list, list) {
>> + br_sysfs_removeif(p);
>> del_nbp(p);
>> }
>>
>> @@ -435,6 +436,7 @@ int br_del_if(struct net_bridge *br, struct net_device *dev)
>> if (!p || p->br != br)
>> return -EINVAL;
>>
>> + br_sysfs_removeif(p);
>> del_nbp(p);
>>
>> spin_lock_bh(&br->lock);
>> diff --git a/net/bridge/br_sysfs_if.c b/net/bridge/br_sysfs_if.c
>> index 7f80462..9e9d17c 100644
>> --- a/net/bridge/br_sysfs_if.c
>> +++ b/net/bridge/br_sysfs_if.c
>> @@ -226,10 +226,17 @@ int br_sysfs_addif(struct net_bridge_port *p)
>> for (a = brport_attrs; *a; ++a) {
>> err = sysfs_create_file(&p->kobj, &((*a)->attr));
>> if (err)
>> - goto out2;
>> + goto out1;
>> }
>>
>> err = sysfs_create_link(br->ifobj, &p->kobj, p->dev->name);
>> + if (err)
>> + goto out1;
>> + return 0;
>> +out1:
>> + for (a = brport_attrs; *a; ++a)
>> + sysfs_remove_file(&p->kobj, &((*a)->attr));
>> + sysfs_remove_link(&br->dev->dev.kobj, SYSFS_BRIDGE_PORT_LINK);
>> out2:
>> return err;
>> }
>
> This is unneeded since the bridge port kobject is deleted when removed
> or in case of error and kobject_del calls sysfs_remove_dir.
>
Stephen, thank you for your explanation.
Since kobject_del will unwind what sysfs_create_* did,
I also think this patch is unneeded.
David, would you please ignore this patch.
next prev parent reply other threads:[~2008-06-21 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:55 [PATCH net-next 4/8] bridge: sysfs cleanup Wang Chen
2008-06-20 1:19 ` Stephen Hemminger
2008-06-20 2:17 ` Wang Chen
2008-06-20 4:48 ` Wang Chen
2008-06-20 17:44 ` Stephen Hemminger
2008-06-21 3:41 ` Wang Chen [this message]
2008-06-21 3:48 ` 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=485C786A.8040204@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).