From: Amir Noam <amir.noam@intel.com>
To: jgarzik@pobox.com, davem@redhat.com
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [PATCH] [bonding 2.4] fix creating/destroying the /proc/net/bonding dir
Date: Tue, 11 Nov 2003 12:32:01 +0200 [thread overview]
Message-ID: <200311111232.01428.amir.noam@intel.com> (raw)
Hi,
Since 2.4.23-rc1 is out, I'm resending this patch that fixes a problem
in the creation/destruction of the /proc/net/bonding dir, introduced
in 2.4.23-pre5.
Please apply.
Amir
diff -Narup a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
--- a/drivers/net/bonding/bond_main.c Thu Oct 23 14:47:31 2003
+++ b/drivers/net/bonding/bond_main.c Thu Oct 23 17:04:52 2003
@@ -3574,6 +3574,62 @@ static void bond_destroy_proc_info(struc
bond->bond_proc_file = NULL;
}
}
+
+/* Create the bonding directory under /proc/net, if doesn't exist yet.
+ * Caller must hold rtnl_lock.
+ */
+static void bond_create_proc_dir(void)
+{
+ int len = strlen(DRV_NAME);
+
+ for (bond_proc_dir = proc_net->subdir; bond_proc_dir;
+ bond_proc_dir = bond_proc_dir->next) {
+ if ((bond_proc_dir->namelen == len) &&
+ !memcmp(bond_proc_dir->name, DRV_NAME, len)) {
+ break;
+ }
+ }
+
+ if (!bond_proc_dir) {
+ bond_proc_dir = proc_mkdir(DRV_NAME, proc_net);
+ if (bond_proc_dir) {
+ bond_proc_dir->owner = THIS_MODULE;
+ } else {
+ printk(KERN_WARNING DRV_NAME
+ ": Warning: cannot create /proc/net/%s\n",
+ DRV_NAME);
+ }
+ }
+}
+
+/* Destroy the bonding directory under /proc/net, if empty.
+ * Caller must hold rtnl_lock.
+ */
+static void bond_destroy_proc_dir(void)
+{
+ struct proc_dir_entry *de;
+
+ if (!bond_proc_dir) {
+ return;
+ }
+
+ /* verify that the /proc dir is empty */
+ for (de = bond_proc_dir->subdir; de; de = de->next) {
+ /* ignore . and .. */
+ if (*(de->name) != '.') {
+ break;
+ }
+ }
+
+ if (de) {
+ if (bond_proc_dir->owner == THIS_MODULE) {
+ bond_proc_dir->owner = NULL;
+ }
+ } else {
+ remove_proc_entry(DRV_NAME, proc_net);
+ bond_proc_dir = NULL;
+ }
+}
#endif /* CONFIG_PROC_FS */
/*
@@ -3829,6 +3885,9 @@ static struct notifier_block bond_netdev
.notifier_call = bond_netdev_event,
};
+/* De-initialize device specific data.
+ * Caller must hold rtnl_lock.
+ */
static inline void bond_deinit(struct net_device *dev)
{
struct bonding *bond = dev->priv;
@@ -3840,6 +3899,9 @@ static inline void bond_deinit(struct ne
#endif
}
+/* Unregister and free all bond devices.
+ * Caller must hold rtnl_lock.
+ */
static void bond_free_all(void)
{
struct bonding *bond, *nxt;
@@ -3847,16 +3909,13 @@ static void bond_free_all(void)
list_for_each_entry_safe(bond, nxt, &bond_dev_list, bond_list) {
struct net_device *dev = bond->device;
- unregister_netdev(dev);
+ unregister_netdevice(dev);
bond_deinit(dev);
free_netdev(dev);
}
#ifdef CONFIG_PROC_FS
- if (bond_proc_dir) {
- remove_proc_entry(DRV_NAME, proc_net);
- bond_proc_dir = NULL;
- }
+ bond_destroy_proc_dir();
#endif
}
@@ -4234,18 +4293,12 @@ static int __init bonding_init(void)
primary = NULL;
}
+ rtnl_lock();
+
#ifdef CONFIG_PROC_FS
- bond_proc_dir = proc_mkdir(DRV_NAME, proc_net);
- if (bond_proc_dir == NULL) {
- printk(KERN_WARNING
- "bonding_init(): can not create /proc/net/" DRV_NAME);
- } else {
- bond_proc_dir->owner = THIS_MODULE;
- }
+ bond_create_proc_dir();
#endif
- rtnl_lock();
-
err = 0;
for (no = 0; no < max_bonds; no++) {
struct net_device *dev;
@@ -4288,18 +4341,21 @@ static int __init bonding_init(void)
return 0;
out_err:
- rtnl_unlock();
-
/* free and unregister all bonds that were successfully added */
bond_free_all();
+ rtnl_unlock();
+
return err;
}
static void __exit bonding_exit(void)
{
unregister_netdevice_notifier(&bond_netdev_notifier);
+
+ rtnl_lock();
bond_free_all();
+ rtnl_unlock();
}
module_init(bonding_init);
next reply other threads:[~2003-11-11 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 10:32 Amir Noam [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 18:08 [PATCH] [bonding 2.4] fix creating/destroying the /proc/net/bonding dir Jay Vosburgh
2003-10-23 15:39 Amir Noam
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=200311111232.01428.amir.noam@intel.com \
--to=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).