public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhao\, Gang" <gamerh2o@gmail.com>
To: Alan <gnomes@lxorguk.ukuu.org.uk>
Cc: devel@driverdev.osuosl.org, mark.einon@gmail.com,
	linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH] et131x: fix allocation failures
Date: Wed, 19 Feb 2014 09:14:19 +0800	[thread overview]
Message-ID: <874n3v52fo.fsf@will.lan> (raw)
In-Reply-To: <20140217141252.26738.33549.stgit@alan.etchedpixels.co.uk> (Alan's message of "Mon, 17 Feb 2014 14:13:08 +0000")

Alan, thanks for resending this patch. But it seems you overlooked
something we discussed earlier.

On Mon, 2014-02-17 at 22:13:08 +0800, Alan wrote:
> We should check the ring allocations don't fail.
> If we get a fail we need to clean up properly. The allocator assumes the
> deallocator will be used on failure, but it isn't. Make sure the
> right deallocator is always called and add a missing check against
> fbr allocation failure.
>
> [v2]: Correct check logic
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>  drivers/staging/et131x/et131x.c |    9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/et131x/et131x.c b/drivers/staging/et131x/et131x.c
> index 6413500..cc600df 100644
> --- a/drivers/staging/et131x/et131x.c
> +++ b/drivers/staging/et131x/et131x.c
> @@ -2124,7 +2124,11 @@ static int et131x_rx_dma_memory_alloc(struct et131x_adapter *adapter)
>  
>  	/* Alloc memory for the lookup table */
>  	rx_ring->fbr[0] = kmalloc(sizeof(struct fbr_lookup), GFP_KERNEL);
> +	if (rx_ring->fbr[0] == NULL)
> +		return -ENOMEM;
>  	rx_ring->fbr[1] = kmalloc(sizeof(struct fbr_lookup), GFP_KERNEL);
> +	if (rx_ring->fbr[1] == NULL)
> +		return -ENOMEM;

Shouldn't rx_ring->fbr[0] be freed when allocation of rx_ring->fbr[1]
fails ? Or we will leak memory here.

>  
>  	/* The first thing we will do is configure the sizes of the buffer
>  	 * rings. These will change based on jumbo packet support.  Larger
> @@ -2289,7 +2293,7 @@ static void et131x_rx_dma_memory_free(struct et131x_adapter *adapter)
>  	for (id = 0; id < NUM_FBRS; id++) {
>  		fbr = rx_ring->fbr[id];
>  
> -		if (!fbr->ring_virtaddr)
> +		if (!fbr || !fbr->ring_virtaddr)
>  			continue;
>  
>  		/* First the packet memory */
> @@ -3591,6 +3595,7 @@ static int et131x_adapter_memory_alloc(struct et131x_adapter *adapter)
>  	if (status) {
>  		dev_err(&adapter->pdev->dev,
>  			  "et131x_tx_dma_memory_alloc FAILED\n");
> +		et131x_tx_dma_memory_free(adapter);
>  		return status;
>  	}
>  	/* Receive buffer memory allocation */
> @@ -3598,7 +3603,7 @@ static int et131x_adapter_memory_alloc(struct et131x_adapter *adapter)
>  	if (status) {
>  		dev_err(&adapter->pdev->dev,
>  			  "et131x_rx_dma_memory_alloc FAILED\n");
> -		et131x_tx_dma_memory_free(adapter);
> +		et131x_adapter_memory_free(adapter);
>  		return status;
>  	}
>  

  reply	other threads:[~2014-02-19  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 14:13 [PATCH] et131x: fix allocation failures Alan
2014-02-19  1:14 ` Zhao, Gang [this message]
2014-02-19 11:43   ` One Thousand Gnomes
2014-02-20  3:03     ` Zhao, Gang
2014-02-20  9:03       ` Dan Carpenter
2014-02-21  2:00         ` Zhao, Gang

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=874n3v52fo.fsf@will.lan \
    --to=gamerh2o@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.einon@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