From: Paul Moore <paul.moore@hp.com>
To: netdev@vger.kernel.org
Subject: [RFC PATCH v1] tun: Cleanup error handling in tun_set_iff()
Date: Mon, 03 Aug 2009 12:12:43 -0400 [thread overview]
Message-ID: <20090803161242.12947.14620.stgit@flek.lan> (raw)
Convert some pointless gotos into returns and ensure tun_attach() errors are
handled correctly.
Signed-off-by: Paul Moore <paul.moore@hp.com>
--
I'm sending this as an RFC patch because I'm not entirely certain that the
changes to the tun_attach() error handling code are 100% correct, although I
strongly suspect that the current behavor of simply returning an error code
without any cleanup is broken. Can anyone comment on this?
---
drivers/net/tun.c | 19 ++++++++++---------
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/net/tun.c b/drivers/net/tun.c
index 4a0db7a..b6d06fd 100644
--- a/drivers/net/tun.c
+++ b/drivers/net/tun.c
@@ -938,13 +938,10 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
err = tun_attach(tun, file);
if (err < 0)
return err;
- }
- else {
+ } else {
char *name;
unsigned long flags = 0;
- err = -EINVAL;
-
if (!capable(CAP_NET_ADMIN))
return -EPERM;
@@ -958,7 +955,7 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
flags |= TUN_TAP_DEV;
name = "tap%d";
} else
- goto failed;
+ return -EINVAL;
if (*ifr->ifr_name)
name = ifr->ifr_name;
@@ -976,10 +973,11 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
tun->flags = flags;
tun->txflt.count = 0;
- err = -ENOMEM;
sk = sk_alloc(net, AF_UNSPEC, GFP_KERNEL, &tun_proto);
- if (!sk)
+ if (!sk) {
+ err = -ENOMEM;
goto err_free_dev;
+ }
init_waitqueue_head(&tun->socket.wait);
sock_init_data(&tun->socket, sk);
@@ -1010,7 +1008,7 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
err = tun_attach(tun, file);
if (err < 0)
- goto failed;
+ goto err_unreg_dev;
}
DBG(KERN_INFO "%s: tun_set_iff\n", tun->dev->name);
@@ -1039,11 +1037,14 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
strcpy(ifr->ifr_name, tun->dev->name);
return 0;
+ err_unreg_dev:
+ rtnl_lock();
+ unregister_netdevice(tun->dev);
+ rtnl_unlock();
err_free_sk:
sock_put(sk);
err_free_dev:
free_netdev(dev);
- failed:
return err;
}
next reply other threads:[~2009-08-03 16:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 16:12 Paul Moore [this message]
2009-08-04 4:16 ` [RFC PATCH v1] tun: Cleanup error handling in tun_set_iff() David Miller
2009-08-05 5:32 ` Eric W. Biederman
2009-08-05 21:38 ` Paul Moore
2009-08-05 23:14 ` Eric W. Biederman
2009-08-06 18:20 ` Paul Moore
2009-08-07 0:00 ` Herbert Xu
2009-08-07 12:23 ` Paul Moore
2009-08-06 10:10 ` Herbert Xu
2009-08-06 10:21 ` Eric W. Biederman
2009-08-06 13:37 ` Herbert Xu
2009-08-06 14:27 ` Eric W. Biederman
2009-08-06 14:39 ` Herbert Xu
2009-08-06 15:02 ` Eric W. Biederman
2009-08-06 18:09 ` Paul Moore
2009-08-06 18:41 ` David Miller
2009-08-07 0:22 ` Herbert Xu
2009-08-07 3:40 ` David Miller
2009-08-07 4:22 ` Eric W. Biederman
2009-08-10 4:52 ` 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=20090803161242.12947.14620.stgit@flek.lan \
--to=paul.moore@hp.com \
--cc=netdev@vger.kernel.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).