linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net
Subject: Re: [PATCH] rt2x00: Remove duplicate deinitialization
Date: Fri, 20 Jun 2008 23:48:58 +0200	[thread overview]
Message-ID: <485C25CA.6000607@kpnplanet.nl> (raw)
In-Reply-To: <200806202210.54248.IvDoorn@gmail.com>

Hi Ivo,


Ivo van Doorn wrote:
> When rt2x00queue_alloc_rxskbs() fails rt2x00queue_unitialize()
> will be called which will free all rxskb. So we don't need
> to do this in the rt2x00queue_alloc_rxskb() function as well.
>
> rt2x00queue_free_skb() unmaps the DMA but doesn't clear the
> allocation flag. Since the code is copied from rt2x00queue_unmap_skb()
> anyway (and that function does clear the flag) we might as well
> use that function directly.
>
> Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
> ---
>
> This patch depends on patches from the pull request of June 16
>
>  drivers/net/wireless/rt2x00/rt2x00queue.c |   20 ++------------------
>  1 files changed, 2 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2x00queue.c b/drivers/net/wireless/rt2x00/rt2x00queue.c
> index 49d3bb8..8e86611 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00queue.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00queue.c
> @@ -107,18 +107,7 @@ void rt2x00queue_unmap_skb(struct rt2x00_dev *rt2x00dev, struct sk_buff *skb)
>  
>  void rt2x00queue_free_skb(struct rt2x00_dev *rt2x00dev, struct sk_buff *skb)
>  {
> -	struct skb_frame_desc *skbdesc = get_skb_frame_desc(skb);
> -
> -	if (skbdesc->flags & SKBDESC_DMA_MAPPED_RX) {
> -		dma_unmap_single(rt2x00dev->dev, skbdesc->skb_dma, skb->len,
> -				 DMA_FROM_DEVICE);
> -	}
> -
> -	if (skbdesc->flags & SKBDESC_DMA_MAPPED_TX) {
> -		dma_unmap_single(rt2x00dev->dev, skbdesc->skb_dma, skb->len,
> -				 DMA_TO_DEVICE);
> -	}
> -
> +	rt2x00queue_unmap_skb(rt2x00dev, skb);
>  	dev_kfree_skb_any(skb);
>  }
>  
> @@ -509,16 +498,11 @@ static int rt2x00queue_alloc_rxskbs(struct rt2x00_dev *rt2x00dev,
>  	for (i = 0; i < queue->limit; i++) {
>  		skb = rt2x00queue_alloc_rxskb(rt2x00dev, &queue->entries[i]);
>  		if (!skb)
> -			goto exit;
> +			return -ENOMEM;
>  		queue->entries[i].skb = skb;
>  	}
>  
>  	return 0;
> -
> -exit:
> -	rt2x00queue_free_skbs(rt2x00dev, queue);
> -
> -	return -ENOMEM;
>  }
>  
>  int rt2x00queue_initialize(struct rt2x00_dev *rt2x00dev)
>   


I find this last hunk of the patch a bit dubious. IMHO a function should 
never rely on letting his caller do the right thing and clean up for it, 
in case of failures; it should always clean up after itself. It is true 
that in this case the caller will also attempt to clean up these 
structures, but that doesn't mean that any potential future users of 
such a function should be bothered with doing the same thing.

---
Gertjan

  reply	other threads:[~2008-06-20 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 20:10 [PATCH] rt2x00: Remove duplicate deinitialization Ivo van Doorn
2008-06-20 21:48 ` Gertjan van Wingerde [this message]
2008-06-21 10:04   ` Ivo van Doorn

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=485C25CA.6000607@kpnplanet.nl \
    --to=gwingerde@kpnplanet.nl \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).