All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org, netdev@vger.kernel.org, ian.campbell@citrix.com
Subject: Re: [Xen-devel] [PATCH net-next V2] xen-netfront: avoid leaking resources when setup_netfront fails
Date: Mon, 20 May 2013 15:24:12 -0400	[thread overview]
Message-ID: <20130520192412.GA29728@phenom.dumpdata.com> (raw)
In-Reply-To: <1369047912-31901-1-git-send-email-wei.liu2@citrix.com>

On Mon, May 20, 2013 at 12:05:12PM +0100, Wei Liu wrote:
> We should correctly free related resources (grant ref, memory page, evtchn)
> when setup_netfront fails.

Looks ok to me.
> 
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> ---
>  drivers/net/xen-netfront.c |   33 +++++++++++++++++++++------------
>  1 file changed, 21 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c
> index 1db10141..5770e3b 100644
> --- a/drivers/net/xen-netfront.c
> +++ b/drivers/net/xen-netfront.c
> @@ -1532,40 +1532,49 @@ static int setup_netfront(struct xenbus_device *dev, struct netfront_info *info)
>  	FRONT_RING_INIT(&info->tx, txs, PAGE_SIZE);
>  
>  	err = xenbus_grant_ring(dev, virt_to_mfn(txs));
> -	if (err < 0) {
> -		free_page((unsigned long)txs);
> -		goto fail;
> -	}
> +	if (err < 0)
> +		goto grant_tx_ring_fail;
>  
>  	info->tx_ring_ref = err;
>  	rxs = (struct xen_netif_rx_sring *)get_zeroed_page(GFP_NOIO | __GFP_HIGH);
>  	if (!rxs) {
>  		err = -ENOMEM;
>  		xenbus_dev_fatal(dev, err, "allocating rx ring page");
> -		goto fail;
> +		goto alloc_rx_ring_fail;
>  	}
>  	SHARED_RING_INIT(rxs);
>  	FRONT_RING_INIT(&info->rx, rxs, PAGE_SIZE);
>  
>  	err = xenbus_grant_ring(dev, virt_to_mfn(rxs));
> -	if (err < 0) {
> -		free_page((unsigned long)rxs);
> -		goto fail;
> -	}
> +	if (err < 0)
> +		goto grant_rx_ring_fail;
>  	info->rx_ring_ref = err;
>  
>  	err = xenbus_alloc_evtchn(dev, &info->evtchn);
>  	if (err)
> -		goto fail;
> +		goto alloc_evtchn_fail;
>  
>  	err = bind_evtchn_to_irqhandler(info->evtchn, xennet_interrupt,
>  					0, netdev->name, netdev);
>  	if (err < 0)
> -		goto fail;
> +		goto bind_fail;
>  	netdev->irq = err;
>  	return 0;
>  
> - fail:
> +	/* If we fail to setup netfront, it is safe to just revoke access to
> +	 * granted pages because backend is not accessing it at this point.
> +	 */
> +bind_fail:
> +	xenbus_free_evtchn(dev, info->evtchn);
> +alloc_evtchn_fail:
> +	gnttab_end_foreign_access_ref(info->rx_ring_ref, 0);
> +grant_rx_ring_fail:
> +	free_page((unsigned long)rxs);
> +alloc_rx_ring_fail:
> +	gnttab_end_foreign_access_ref(info->tx_ring_ref, 0);
> +grant_tx_ring_fail:
> +	free_page((unsigned long)txs);
> +fail:
>  	return err;
>  }
>  
> -- 
> 1.7.10.4
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-05-20 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 11:05 [PATCH net-next V2] xen-netfront: avoid leaking resources when setup_netfront fails Wei Liu
2013-05-20 19:24 ` Konrad Rzeszutek Wilk [this message]
2013-05-20 19:24 ` Konrad Rzeszutek Wilk
2013-05-20 20:43 ` David Miller
2013-05-20 20:43 ` 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=20130520192412.GA29728@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 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.