From: Jason Wang <jasowang@redhat.com>
To: Girish Moodalbail <girish.moodalbail@oracle.com>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] tap: double-free in error path in tap_open()
Date: Wed, 25 Oct 2017 09:55:40 +0800 [thread overview]
Message-ID: <e5816501-b58c-506c-161f-8ee7a80ea347@redhat.com> (raw)
In-Reply-To: <1508881270-4124-1-git-send-email-girish.moodalbail@oracle.com>
On 2017年10月25日 05:41, Girish Moodalbail wrote:
> Double free of skb_array in tap module is causing kernel panic. When
> tap_set_queue() fails we free skb_array right away by calling
> skb_array_cleanup(). However, later on skb_array_cleanup() is called
> again by tap_sock_destruct through sock_put(). This patch fixes that
> issue.
>
> Fixes: 362899b8725b35e3 (macvtap: switch to use skb array)
> Signed-off-by: Girish Moodalbail <girish.moodalbail@oracle.com>
> ---
> drivers/net/tap.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/tap.c b/drivers/net/tap.c
> index 21b71ae..878520b 100644
> --- a/drivers/net/tap.c
> +++ b/drivers/net/tap.c
> @@ -542,20 +542,20 @@ static int tap_open(struct inode *inode, struct file *file)
>
> err = -ENOMEM;
> if (skb_array_init(&q->skb_array, tap->dev->tx_queue_len, GFP_KERNEL))
> - goto err_array;
> + goto err_put;
Looks like this will cause skb_array_cleanup() to be called when skb
array was uninitialized?
Thanks
>
> err = tap_set_queue(tap, file, q);
> - if (err)
> - goto err_queue;
> + if (err) {
> + /* tap_sock_destruct() will take care of freeing skb_array */
> + goto err_put;
> + }
>
> dev_put(tap->dev);
>
> rtnl_unlock();
> return err;
>
> -err_queue:
> - skb_array_cleanup(&q->skb_array);
> -err_array:
> +err_put:
> sock_put(&q->sk);
> err:
> if (tap)
next prev parent reply other threads:[~2017-10-25 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 21:41 [PATCH] tap: double-free in error path in tap_open() Girish Moodalbail
2017-10-25 1:55 ` Jason Wang [this message]
2017-10-25 4:07 ` Girish Moodalbail
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=e5816501-b58c-506c-161f-8ee7a80ea347@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=girish.moodalbail@oracle.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