From: Jason Wang <jasowang@redhat.com>
To: Cong Wang <xiyou.wangcong@gmail.com>, netdev@vger.kernel.org
Cc: dvyukov@google.com
Subject: Re: [Patch net v3] tun: fix a memory leak for tfile->tx_array
Date: Tue, 16 Jan 2018 13:46:40 +0800 [thread overview]
Message-ID: <3c47b1dd-f8ae-87a7-a498-467b9027dcbc@redhat.com> (raw)
In-Reply-To: <20180115193729.13220-1-xiyou.wangcong@gmail.com>
On 2018年01月16日 03:37, Cong Wang wrote:
> tfile->tun could be detached before we close the tun fd,
> via tun_detach_all(), so it should not be used to check for
> tfile->tx_array.
>
> As Jason suggested, we probably have to clean it up
> unconditionally both in __tun_deatch() and tun_detach_all(),
> but this requires to check if it is initialized or not.
> Currently skb_array_cleanup() doesn't have such a check,
> so I check it in the caller and introduce a helper function,
> it is a bit ugly but we can always improve it in net-next.
>
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Fixes: 1576d9860599 ("tun: switch to use skb array for tx")
> Cc: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> ---
> drivers/net/tun.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 4f4a842a1c9c..a8ec589d1359 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -611,6 +611,14 @@ static void tun_queue_purge(struct tun_file *tfile)
> skb_queue_purge(&tfile->sk.sk_error_queue);
> }
>
> +static void tun_cleanup_tx_array(struct tun_file *tfile)
> +{
> + if (tfile->tx_array.ring.queue) {
> + skb_array_cleanup(&tfile->tx_array);
> + memset(&tfile->tx_array, 0, sizeof(tfile->tx_array));
> + }
> +}
> +
> static void __tun_detach(struct tun_file *tfile, bool clean)
> {
> struct tun_file *ntfile;
> @@ -657,8 +665,7 @@ static void __tun_detach(struct tun_file *tfile, bool clean)
> tun->dev->reg_state == NETREG_REGISTERED)
> unregister_netdevice(tun->dev);
> }
> - if (tun)
> - skb_array_cleanup(&tfile->tx_array);
> + tun_cleanup_tx_array(tfile);
> sock_put(&tfile->sk);
> }
> }
> @@ -700,11 +707,13 @@ static void tun_detach_all(struct net_device *dev)
> /* Drop read queue */
> tun_queue_purge(tfile);
> sock_put(&tfile->sk);
> + tun_cleanup_tx_array(tfile);
> }
> list_for_each_entry_safe(tfile, tmp, &tun->disabled, next) {
> tun_enable_queue(tfile);
> tun_queue_purge(tfile);
> sock_put(&tfile->sk);
> + tun_cleanup_tx_array(tfile);
> }
> BUG_ON(tun->numdisabled != 0);
>
> @@ -2851,6 +2860,8 @@ static int tun_chr_open(struct inode *inode, struct file * file)
>
> sock_set_flag(&tfile->sk, SOCK_ZEROCOPY);
>
> + memset(&tfile->tx_array, 0, sizeof(tfile->tx_array));
> +
> return 0;
> }
>
I think then you don't even need the memset trick since we are sure it
has been implemented?
Thanks
next prev parent reply other threads:[~2018-01-16 5:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 19:37 [Patch net v3] tun: fix a memory leak for tfile->tx_array Cong Wang
2018-01-16 5:46 ` Jason Wang [this message]
2018-01-16 5:49 ` Cong Wang
2018-01-16 6:00 ` Jason Wang
2018-01-16 6:07 ` Cong Wang
2018-01-16 6:12 ` Jason Wang
2018-01-16 6:33 ` Cong Wang
2018-01-16 6:37 ` Jason Wang
2018-01-16 6:49 ` Cong Wang
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=3c47b1dd-f8ae-87a7-a498-467b9027dcbc@redhat.com \
--to=jasowang@redhat.com \
--cc=dvyukov@google.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).