From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: don't clear all tx flags when requeing
Date: Fri, 17 Jul 2015 11:09:59 +0200 [thread overview]
Message-ID: <1437124199.1933.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1437124038.1933.4.camel@sipsolutions.net> (sfid-20150717_110753_137870_576AC4E6)
On Fri, 2015-07-17 at 11:07 +0200, Johannes Berg wrote:
>
> > > Once (a) is not stripped (b) becomes important
> > > because it's the main condition to clear the
> > > Service Period bit of the station when Tx status
> > > for the released frame is reported back.
> > >
> > > This problem was observed with ath9k acting as P2P
> > > GO in some testing scenarios but isn't limited to
> > > it. AP operation with mac80211 based Tx A-MPDU
> > > control combined with clients using PS-Poll frames
> > > is subject to this race.
> >
> > I'm not sure I quite understand - how is the aggregation teardown
> > causing frame filtering?
> >
>
> Never mind, I was looking at the wrong code. I'll apply this.
>
However, I'd like to ask you to look at this again - I can see how it
fixes the problem now, but it seems like a fairly unreliable fix since
the frame is sent through TX processing again, and you're relying on
that preserving a flag that's otherwise marked temporary...
So I think it may be better to adjust the station flags in this case to
let a new (the same) frame be the ps-poll response again.
johannes
next prev parent reply other threads:[~2015-07-17 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 7:59 [PATCH] mac80211: don't clear all tx flags when requeing Michal Kazior
2015-07-17 9:05 ` Johannes Berg
2015-07-17 9:07 ` Johannes Berg
2015-07-17 9:09 ` Johannes Berg [this message]
2015-07-17 9:35 ` Michal Kazior
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=1437124199.1933.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).