From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RFC: Hashing by VIF addr for rx of data packets.
Date: Wed, 03 Apr 2013 15:42:23 +0200 [thread overview]
Message-ID: <1364996543.8351.42.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <515C308F.7030506@candelatech.com>
On Wed, 2013-04-03 at 06:37 -0700, Ben Greear wrote:
> > Hmmm. I'm not really convinced this will make sense upstream. I'm kinda
> > fine with the single-station cache, but maintaining a whole other hash
> > table seems too much overhead for every use case but yours.
>
> Yeah, aside from multiple stations, I'm not sure it helps anything. It would
> require a different scheme to help with multiple VAP I think, and I'm not
> sure there are any other multi-vif use cases out there...
Yes, likely.
> >> + if (!is_multicast_ether_addr(hdr->addr1)) {
> >> + sta = sta_info_get_by_vif(local, hdr->addr1);
> >
> > AFAICT, this is also wrong for TDLS and other cases where we might
> > receive a frame that's not from the AP, even if it's only by accident or
> > from an attacker.
>
> I think patch is probably wrong for any VIF that can be associated with more than
> one station (such as APs). I'm going to re-work the vhash to only include
> Station VIFS and see how that works for my test case.
Well it's wrong even as is, even with just a single station on that VIF,
because as far as I can tell it assumes that *any* frame, no matter who
it came from, was from that station.
johannes
prev parent reply other threads:[~2013-04-03 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 23:45 RFC: Hashing by VIF addr for rx of data packets Ben Greear
2013-04-03 12:46 ` Johannes Berg
2013-04-03 13:37 ` Ben Greear
2013-04-03 13:42 ` Johannes Berg [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=1364996543.8351.42.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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).