public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Pedro Marzo Perez <marzo.pedro@gmail.com>
Cc: gregkh@linuxfoundation.org, navyasri.tech@gmail.com,
	dilekuzulmez@gmail.com, joe@perches.com,
	haticeerturk27@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3 v3] Staging: rtl8192u: Simplify error check code at prism2_wep_init
Date: Wed, 20 May 2015 00:46:55 +0300	[thread overview]
Message-ID: <20150519214655.GE4150@mwanda> (raw)
In-Reply-To: <1431991944-16924-2-git-send-email-marzo.pedro@gmail.com>

I was planning to leave this one for Greg but since you asked me to
comment...

This patch is ok as one patch.  The subject is "clean up
prism2_wep_init()" and that's one thing.  Breaking it up into tiny
patches would probably make it harder to review.

On Tue, May 19, 2015 at 01:32:22AM +0200, Pedro Marzo Perez wrote:
> Merge two pr_debug lines with literal strings splitted across several lines
> into one single line, simplifying prism2_wep_init error check code.
> 
> Signed-off-by: Pedro Marzo Perez <marzo.pedro@gmail.com>
> ---
>  .../rtl8192u/ieee80211/ieee80211_crypt_wep.c       | 22 +++++++++-------------
>  1 file changed, 9 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> index 0a17f84..388ed3c 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> @@ -9,6 +9,8 @@
>   * more details.
>   */
>  
> +#define pr_fmt(fmt) "ieee80211_crypt_wep: " fmt

Greg doesn't like pr_fmt() in driver code, use dev_dbg() and friends
instead.  I don't like debug output generally so I say just delete it.
Especially in this case the debug output is pretty useless.

> +
>  #include <linux/module.h>
>  #include <linux/init.h>
>  #include <linux/slab.h>
> @@ -43,20 +45,16 @@ static void *prism2_wep_init(int keyidx)
>  
>  	priv = kzalloc(sizeof(*priv), GFP_ATOMIC);
>  	if (priv == NULL)
> -		goto fail;
> +		return NULL;
>  	priv->key_idx = keyidx;
>  
>  	priv->tx_tfm = crypto_alloc_blkcipher("ecb(arc4)", 0, CRYPTO_ALG_ASYNC);
>  	if (IS_ERR(priv->tx_tfm)) {
> -		pr_debug("ieee80211_crypt_wep: could not allocate "
> -		       "crypto API arc4\n");
>  		priv->tx_tfm = NULL;
>  		goto fail;

This error handling is overly complicated.  It's supposed to be you
climb up a mountain to go hang gliding (return zero), but if you hit an
error on the way to the talk you walk backwards the way you came to the
bottom of the mountain.  You see all the landmarks in reverse order and
it makes you have a sad face.

allocate priv
allocate tx
allocate rx

return success;  <-- made it to the top

free tx <- walking back down.  :(
free priv

It should be:

	if (IS_ERR(priv->tx_tfm))
		goto free_priv;

>  	}
>  	priv->rx_tfm = crypto_alloc_blkcipher("ecb(arc4)", 0, CRYPTO_ALG_ASYNC);
>  	if (IS_ERR(priv->rx_tfm)) {
> -		pr_debug("ieee80211_crypt_wep: could not allocate "
> -		       "crypto API arc4\n");
>  		priv->rx_tfm = NULL;
>  		goto fail;
>  	}

	if (IS_ERR(priv->rx_tfm))
		goto free_tx;

If this allocation succeeds then we've made it to the top.  No need to
call crypto_free_blkcipher(priv->rx_tfm) in this function.

> @@ -67,14 +65,12 @@ static void *prism2_wep_init(int keyidx)
>  	return priv;
>  
>  fail:
> -	if (priv) {
> -		if (priv->tx_tfm)
> -			crypto_free_blkcipher(priv->tx_tfm);
> -		if (priv->rx_tfm)
> -			crypto_free_blkcipher(priv->rx_tfm);
> -		kfree(priv);
> -	}

In the original code there isn't a nice error path down the mountain,
it's all mixed together and not in any particular order.

> -
> +	pr_debug("could not allocate crypto API arc4\n");
> +	if (priv->tx_tfm)
> +		crypto_free_blkcipher(priv->tx_tfm);
> +	if (priv->rx_tfm)
> +		crypto_free_blkcipher(priv->rx_tfm);
> +	kfree(priv);
>  	return NULL;


free_tx:
	crypto_free_blkcipher(priv->tx_tfm);
free_priv:
	kfree(priv);

	return NULL;

regards,
dan carpenter

  parent reply	other threads:[~2015-05-19 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 23:32 [PATCH 0/3 v3] Staging: rtl8192u: Fix coding style issues at ieee80211_crypt_wep.c Pedro Marzo Perez
2015-05-18 23:32 ` [PATCH 1/3 v3] Staging: rtl8192u: Simplify error check code at prism2_wep_init Pedro Marzo Perez
2015-05-19  5:34   ` Sudip Mukherjee
2015-05-19 22:49     ` pmarzo
2015-05-19 21:46   ` Dan Carpenter [this message]
2015-05-20  8:26     ` pmarzo
2015-05-20  9:03       ` Dan Carpenter
2015-05-31  1:36   ` Greg KH
2015-05-18 23:32 ` [PATCH 2/3 v3] Staging: rtl8192u: Remove two useless lines at ieee80211_wep_null Pedro Marzo Perez
2015-05-31  1:37   ` Greg KH
2015-05-18 23:32 ` [PATCH 3/3 v3] Staging: rtl8192u: Correct include indentation and openning braces at new line Pedro Marzo Perez

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=20150519214655.GE4150@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dilekuzulmez@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haticeerturk27@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marzo.pedro@gmail.com \
    --cc=navyasri.tech@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