From: Christian Lamparter <chunkeey@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix RX aggregation locking
Date: Mon, 29 Nov 2010 15:01:11 +0100 [thread overview]
Message-ID: <201011291501.12293.chunkeey@googlemail.com> (raw)
In-Reply-To: <1291025356.3532.1.camel@jlt3.sipsolutions.net>
On Monday 29 November 2010 11:09:16 Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The RX aggregation locking documentation was
> wrong, which led Christian to also code the
> timer timeout handling for it somewhat wrongly.
>
> Fix the documentation, the two places that
> need to hold the reorder lock across accesses
> to the structure, and the debugfs code that
> should just use RCU.
>
> Also, remove acquiring the sta->lock across
> reorder timeouts since it isn't necessary, and
> change a few places to GFP_KERNEL because the
> code path here doesn't need atomic allocations
> as I noticed when reviewing all this.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> Christian, do you remember what else we needed to do here?
Sure, I put a "helpful" comment in commit 15943a72c:
"mac80211: temporarily disable reorder release timer"
including a "list" of things that need to be considered:
http://marc.info/?l=linux-wireless&m=128656352920957
But, one thing, I think I finally found out why the
device keeps disconnecting for some users:
http://www.spinics.net/lists/linux-wireless/msg56678.html
and I need to fix that first :(
Best regards,
Chr
prev parent reply other threads:[~2010-11-29 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 10:09 [PATCH] mac80211: fix RX aggregation locking Johannes Berg
2010-11-29 14:01 ` Christian Lamparter [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=201011291501.12293.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).