Linux wireless drivers development
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [IWL4965] TX Power requested while scanning!
Date: Wed, 27 Apr 2011 12:18:08 +0200	[thread overview]
Message-ID: <1303899488.2050.11.camel@x61.thuisdomein> (raw)
In-Reply-To: <20110426063211.GA2419@redhat.com>

On Tue, 2011-04-26 at 08:32 +0200, Stanislaw Gruszka wrote:
> Warning correctly indicate a bug. Please try below patch.
> 
> diff --git a/drivers/net/wireless/iwlegacy/iwl4965-base.c b/drivers/net/wireless/iwlegacy/iwl4965-base.c
> index 58a2e63..46966e9 100644
> --- a/drivers/net/wireless/iwlegacy/iwl4965-base.c
> +++ b/drivers/net/wireless/iwlegacy/iwl4965-base.c
> @@ -2988,15 +2988,15 @@ static void iwl4965_bg_txpower_work(struct work_struct *work)
>  	struct iwl_priv *priv = container_of(work, struct iwl_priv,
>  			txpower_work);
>  
> +	mutex_lock(&priv->mutex);
> +
>  	/* If a scan happened to start before we got here
>  	 * then just return; the statistics notification will
>  	 * kick off another scheduled work to compensate for
>  	 * any temperature delta we missed here. */
>  	if (test_bit(STATUS_EXIT_PENDING, &priv->status) ||
>  	    test_bit(STATUS_SCANNING, &priv->status))
> -		return;
> -
> -	mutex_lock(&priv->mutex);
> +		goto out;
>  
>  	/* Regardless of if we are associated, we must reconfigure the
>  	 * TX power since frames can be sent on non-radar channels while
> @@ -3006,7 +3006,7 @@ static void iwl4965_bg_txpower_work(struct work_struct *work)
>  	/* Update last_temperature to keep is_calib_needed from running
>  	 * when it isn't needed... */
>  	priv->last_temperature = priv->temperature;
> -
> +out:
>  	mutex_unlock(&priv->mutex);
>  }
>  

0) This (compiles and) runs without apparent problems. I haven't seen
this WARNING with this patch applied. But please note that I actually
haven't seen that WARNING with (unpatched) rc4 since reporting it (last
Friday).

1) So feel free to add a "Reported-by:" tag and, perhaps, a "Tested-by:"
tag too.


Paul Bolle


      reply	other threads:[~2011-04-27 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 18:56 [IWL4965] TX Power requested while scanning! Paul Bolle
2011-04-26  6:32 ` Stanislaw Gruszka
2011-04-27 10:18   ` Paul Bolle [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=1303899488.2050.11.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.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