From: Johannes Berg <johannes@sipsolutions.net>
To: michael-dev <michael-dev@fami-braun.de>
Cc: linux-wireless@vger.kernel.org, projekt-wlan@fem.tu-ilmenau.de,
kvalo@codeaurora.org, akarwar@marvell.com, nishants@marvell.com,
Larry.Finger@lwfinger.net, Jes.Sorensen@redhat.com
Subject: Re: [PATCHv4] mac80211: check A-MSDU inner frame source address on AP interfaces
Date: Thu, 06 Oct 2016 13:36:27 +0200 [thread overview]
Message-ID: <1475753787.2015.13.camel@sipsolutions.net> (raw)
In-Reply-To: <bb2ea10f30d2ae8a3cc048974ed148c8@fami-braun.de>
> The rules when to check sa/da should be independent of the driver
> and thus would likely be duplicated by each caller. This is why I
> had it in ieee80211_amsdu_to_8023s.
That does make sense, I guess. But I feel that it's overly complicated,
and most drivers don't actually support all those features, in
particular, 4-addr station/AP is currently exclusive to mac80211.
> My patch defaulted into not checking sa/da for interface type not
> explicitly given, whereas your code defaults to checking both for
> those.
> This makes a difference for IFTYPE_MONITOR, IFTYPE_P2P_*,
Monitor will never get there, and P2P_CLIENT == STATION, P2P_GO == AP
as far as mac80211's vif.type is concerned, so those are handled.
> IFTYPE_OCB,
That can't do A-MSDU I believe.
> IFTYPE_UNSPECIFIED,
That is invalid and can never happen here.
> IFTYPE_WDS.
This is ... it can't even negotiate HT, so I doubt A-MSDU could be used
in any way. This is old crap, and I'd actually rather remove it, the 4-
addr station/AP superseded it.
> I don't know if filtering is appropiate
> for those or if they can actually occur there.
I think it's all covered then.
Could you test my patches in your scenario to see they do what we want?
I'll resend as [PATCH] then, and think about applying them and perhaps
backporting also.
johannes
next prev parent reply other threads:[~2016-10-06 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 10:02 [PATCHv4] mac80211: check A-MSDU inner frame source address on AP interfaces Michael Braun
2016-10-05 14:59 ` Johannes Berg
2016-10-06 11:30 ` michael-dev
2016-10-06 11:36 ` Johannes Berg [this message]
2016-10-08 10:13 ` michael-dev
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=1475753787.2015.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=akarwar@marvell.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael-dev@fami-braun.de \
--cc=nishants@marvell.com \
--cc=projekt-wlan@fem.tu-ilmenau.de \
/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).