From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
wannes.rombouts@epitech.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tuntap: correctly handle error in tun_set_iff()
Date: Wed, 11 Sep 2013 12:38:43 +0300 [thread overview]
Message-ID: <20130911093843.GA20836@redhat.com> (raw)
In-Reply-To: <1378887845-6821-1-git-send-email-jasowang@redhat.com>
On Wed, Sep 11, 2013 at 04:24:05PM +0800, Jason Wang wrote:
> Commit c8d68e6be1c3b242f1c598595830890b65cea64a (tuntap: multiqueue support)
> only call free_netdev() on err in tun_set_iff(). This causes several issues:
>
> - memory of tun security were leaked
Not just tun security - sock reference too (didn't detach)
> - use after free since the flow gc timer was not deleted and the tfile were not
> detached
>
> This patch solves the above issues.
>
> Reported-by: Wannes Rombouts <wannes.rombouts@epitech.eu>
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> The patch were also needed for stable 3.8+.
> ---
> drivers/net/tun.c | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index a639de8..e5fb5d3 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -1641,11 +1641,11 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
> INIT_LIST_HEAD(&tun->disabled);
> err = tun_attach(tun, file, false);
> if (err < 0)
> - goto err_free_dev;
> + goto err_free_flow;
>
> err = register_netdevice(tun->dev);
> if (err < 0)
> - goto err_free_dev;
> + goto err_detach;
>
> if (device_create_file(&tun->dev->dev, &dev_attr_tun_flags) ||
> device_create_file(&tun->dev->dev, &dev_attr_owner) ||
> @@ -1689,6 +1689,11 @@ static int tun_set_iff(struct net *net, struct file *file, struct ifreq *ifr)
> strcpy(ifr->ifr_name, tun->dev->name);
> return 0;
>
> +err_detach:
> + tun_detach_all(dev);
> +err_free_flow:
> + tun_flow_uninit(tun);
> + security_tun_dev_free_security(tun->security);
This bit looks wrong: if flow_init fails, we
need security_tun_dev_free_security, don't we?
I think we need:
+err_free_sec: security_tun_dev_free_security(tun->security);
and goto here on flow_init failures.
> err_free_dev:
Pls shift this one 1 space left for consistency.
> free_netdev(dev);
> return err;
> --
> 1.7.1
next prev parent reply other threads:[~2013-09-11 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 8:24 [PATCH net] tuntap: correctly handle error in tun_set_iff() Jason Wang
2013-09-11 9:38 ` Michael S. Tsirkin [this message]
2013-09-11 9:55 ` Jason Wang
2013-09-11 10:08 ` Michael S. Tsirkin
2013-09-11 10:18 ` Jason Wang
2013-09-11 10:58 ` Michael S. Tsirkin
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=20130911093843.GA20836@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wannes.rombouts@epitech.eu \
/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.