All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org, Touko Korpela <touko.korpela@iki.fi>,
	Arend van Spriel <arend@broadcom.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [PATCH 3.2.y, 3.3.y] brcm80211: smac: fix endless retry of A-MPDU transmissions
Date: Fri, 18 May 2012 12:58:12 -0700	[thread overview]
Message-ID: <20120518195812.GE4874@kroah.com> (raw)
In-Reply-To: <20120516222824.GA11009@burratino>

On Wed, May 16, 2012 at 05:28:25PM -0500, Jonathan Nieder wrote:
> From: Arend van Spriel <arend@broadcom.com>
> Date: Thu, 9 Feb 2012 21:08:58 +0100
> 
> commit 5e379203c7788b7af01150bfadbc74d2797a2ef4 upstream.
> 
> The A-MPDU code checked against a retry limit, but it was using
> the wrong variable to do so. This patch fixes this to assure
> proper retry mechanism.
> 
> This problem had a side-effect causing the mac80211 flush callback
> to remain waiting forever as well. That side effect has been fixed
> by commit by Stanislaw Gruszka:
> 
> commit f96b08a7e6f69c0f0a576554df3df5b1b519c479
> Date:   Tue Jan 17 12:38:50 2012 +0100
> 
>     brcmsmac: fix tx queue flush infinite loop
> 
>     Reference:
>     https://bugzilla.kernel.org/show_bug.cgi?id=42576
> 
> Cc: Stanislaw Gruszka <sgruszka@redhat.com>
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Reviewed-by: Alwin Beukers <alwin@broadcom.com>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> ---
> Hi Ben and Greg,
> 
> Please consider
> 
>   5e379203c778 brcm80211: smac: fix endless retry of A-MPDU
>                transmissions
> 
> for application to the 3.2.y and 3.3.y stable trees.  It is the real
> fix to the bug worked around by f96b08a7e6f6 (brcmsmac: fix tx queue
> flush infinite loop, 2012-01-17).  The remaining symptom after that
> workaround was an assertion failure (WARNING at
> drivers/net/wireless/brcm80211/brcmsmac/main.c:8241).
> 
> Touko Korpela (cc-ed) tested the patch against 3.2.17 + "brcm80211:
> smac: pass missing argument to 'brcms_b_mute'" and found it to
> work[1]:

It doesn't apply to the 3.3-stable tree, so it's a bit hard for me to
apply it...

thanks,

greg k-h

  parent reply	other threads:[~2012-05-18 19:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 17:38 [PATCH for 3.3 0/2] brcm80211: fix endless A-MPDU retries Arend van Spriel
2012-02-23 17:38 ` [PATCH 1/2] brcm80211: smac: fix endless retry of A-MPDU transmissions Arend van Spriel
2012-05-16 22:28   ` [PATCH 3.2.y, 3.3.y] " Jonathan Nieder
2012-05-17  0:05     ` Ben Hutchings
2012-05-18 19:58     ` Greg KH [this message]
2012-05-18 20:51       ` Jonathan Nieder
2012-05-19  8:49         ` Arend van Spriel
2012-05-19 16:53           ` Jonathan Nieder
2012-02-23 17:38 ` [PATCH 2/2] brcm80211: smac: only print block-ack timeout message at trace level Arend van Spriel
2012-11-24 23:14   ` [3.2.y] " Jonathan Nieder
2012-12-02  3:35     ` Ben Hutchings

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=20120518195812.GE4874@kroah.com \
    --to=greg@kroah.com \
    --cc=arend@broadcom.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=touko.korpela@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.