From: Johannes Berg <johannes@sipsolutions.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Don't buffer non-bufferable MMPDUs
Date: Tue, 05 Jan 2016 16:52:36 +0100 [thread overview]
Message-ID: <1452009156.12357.38.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGXE3d9TZbUF0k0moa_hzOUip9q5PgDSe0kDbiD1KCH7mjX+Ng@mail.gmail.com> (sfid-20160105_164357_550938_57AADF44)
On Tue, 2016-01-05 at 16:43 +0100, Helmut Schaa wrote:
> > That said, it obviously also points to a driver bug not treating
> > these frames correctly, so you might want to investigate why you
> > got here to start with!
>
> It was not the driver marking the frame as filtered but mac80211
> itself in status.c:
>
> acked = !!(info->flags & IEEE80211_TX_STAT_ACK);
> if (!acked && test_sta_flag(sta, WLAN_STA_PS_STA)) {
> /*
> * The STA is in power save mode, so assume
> * that this TX packet failed because of
> that.
> */
> ieee80211_handle_filtered_frame(local, sta,
> skb);
> rcu_read_unlock();
> return;
> }
Ah, yes, ok. So the frame simply didn't go through, for whatever
reason. Hopefully the driver actually transmitted it :)
> However, I've put the code into ieee80211_handle_filtered_frame to
> not grow ieee80211_tx_status even more :)
>
> If you prefer to add it here directly I'm fine to change it.
>
No, looks fine as is. I just misunderstood how we got here.
johannes
next prev parent reply other threads:[~2016-01-05 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 14:37 [PATCH] mac80211: Don't buffer non-bufferable MMPDUs Helmut Schaa
2016-01-05 15:35 ` Johannes Berg
2016-01-05 15:43 ` Helmut Schaa
2016-01-05 15:52 ` Johannes Berg [this message]
2016-01-05 15:56 ` Helmut Schaa
2016-01-05 16:42 ` [PATCHv2] " Helmut Schaa
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=1452009156.12357.38.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
/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).