linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rfkill: fix double-mutex-locking
Date: Wed, 28 Nov 2007 21:13:53 +0100	[thread overview]
Message-ID: <200711282113.53874.IvDoorn@gmail.com> (raw)
In-Reply-To: <200711281749.34572.mb@bu3sch.de>

On Wednesday 28 November 2007, Michael Buesch wrote:
> rfkill_toggle_radio is called from functions where
> rfkill->mutex is already aquired.
> 
> Remove the lock from rfkill_toggle_radio() and add it to
> the only calling function that calls it without the lock held.
> 
> Signed-off-by: Michael Buesch <mb@bu3sch.de>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>

> Index: wireless-2.6/net/rfkill/rfkill.c
> ===================================================================
> --- wireless-2.6.orig/net/rfkill/rfkill.c	2007-11-20 19:09:35.000000000 +0100
> +++ wireless-2.6/net/rfkill/rfkill.c	2007-11-28 17:09:55.000000000 +0100
> @@ -60,11 +60,7 @@ static void rfkill_led_trigger(struct rf
>  static int rfkill_toggle_radio(struct rfkill *rfkill,
>  				enum rfkill_state state)
>  {
> -	int retval;
> -
> -	retval = mutex_lock_interruptible(&rfkill->mutex);
> -	if (retval)
> -		return retval;
> +	int retval = 0;
>  
>  	if (state != rfkill->state) {
>  		retval = rfkill->toggle_radio(rfkill->data, state);
> @@ -74,7 +70,6 @@ static int rfkill_toggle_radio(struct rf
>  		}
>  	}
>  
> -	mutex_unlock(&rfkill->mutex);
>  	return retval;
>  }
>  
> @@ -158,12 +153,13 @@ static ssize_t rfkill_state_store(struct
>  	if (!capable(CAP_NET_ADMIN))
>  		return -EPERM;
>  
> +	if (mutex_lock_interruptible(&rfkill->mutex))
> +		return -ERESTARTSYS;
>  	error = rfkill_toggle_radio(rfkill,
>  			state ? RFKILL_STATE_ON : RFKILL_STATE_OFF);
> -	if (error)
> -		return error;
> +	mutex_unlock(&rfkill->mutex);
>  
> -	return count;
> +	return error ? error : count;
>  }
>  
>  static ssize_t rfkill_claim_show(struct device *dev,
> 



      reply	other threads:[~2007-11-28 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 16:49 [PATCH] rfkill: fix double-mutex-locking Michael Buesch
2007-11-28 20:13 ` Ivo van Doorn [this message]

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=200711282113.53874.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).