From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: steven@uplinklabs.net, linux-wireless@vger.kernel.org,
stable@kernel.org, linville@tuxdriver.com
Subject: Re: [stable] [PATCH] ath9k: fix oops on trying to hold the wrong spinlock
Date: Thu, 16 Oct 2008 16:28:47 -0700 [thread overview]
Message-ID: <20081016232847.GA29003@kroah.com> (raw)
In-Reply-To: <43e72e890810161612p69dc838sc6f25f33f5de8631@mail.gmail.com>
On Thu, Oct 16, 2008 at 04:12:02PM -0700, Luis R. Rodriguez wrote:
> On Thu, Oct 16, 2008 at 2:54 PM, Greg KH <greg@kroah.com> wrote:
> > On Thu, Oct 16, 2008 at 04:12:55AM -0700, Luis R. Rodriguez wrote:
> >> This fixes on oops when you get try to send a BA to an 11n AP.
> >> The oops occurred because we were trying to aquire an incorrect
> >> spinlock.
> >>
> >> We were trying to hold the wrong spinlock due to a typo
> >> on IEEE80211_BAR_CTL_TID_S's definition. We use this to
> >> compute the tid number and then hold this this tid number's
> >> spinlock.
> >>
> >> Tested-by: Steven Noonan <steven@uplinklabs.net>
> >> Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>
> >> Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
> >> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> >> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> >> ---
> >>
> >> I don't see this queue'd yet for 2.6.27.2
> >
> > Is it in Linus's tree? If so, do you have a git commit id?
>
> Got it.
>
> a477e4e6d48d3ac7c7a75bad40585cb391e5c237
>
> If you can add the Reported-by tag it'd be great, I missed it on Linus' tree.
You mean the "tested-by" flag? I've added that, I don't see a
reported-by flag above.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-16 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 11:12 [PATCH] ath9k: fix oops on trying to hold the wrong spinlock Luis R. Rodriguez
2008-10-16 21:54 ` [stable] " Greg KH
2008-10-16 23:12 ` Luis R. Rodriguez
2008-10-16 23:28 ` Greg KH [this message]
2008-10-16 23:41 ` Luis R. Rodriguez
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=20081016232847.GA29003@kroah.com \
--to=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=stable@kernel.org \
--cc=steven@uplinklabs.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).