From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Braun <michael-dev@fami-braun.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
projekt-wlan@fem.tu-ilmenau.de
Subject: Re: [PATCHv2 1/1] mac80211: fix WPA with VLAN on AP side with ps-sta
Date: Tue, 12 Feb 2013 17:40:05 +0100 [thread overview]
Message-ID: <1360687205.29913.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1360687114.29913.5.camel@jlt4.sipsolutions.net> (sfid-20130212_173850_784059_F68F7C1F)
On Tue, 2013-02-12 at 17:38 +0100, Johannes Berg wrote:
> On Tue, 2013-02-12 at 17:37 +0100, Michael Braun wrote:
> > When sending a broadcast while at least on of the connected stations is
> > sleeping, it gets queued and send after a DTIM beacon is sent.
> > If the packet was to be sent on a vlan interface, the vif used for dequeing
> > from the per-bss queue does not hold the per-vlan sdata. The correct sdata is
> > required to use the correct per-vlan broadcast/multicast key.
> >
> > This patch fixes this by restoring the per-vlan sdata using the skb->dev entry.
> >
> > Signed-off-by: Michael Braun <michael-dev@fami-braun.de>
> >
> > V2: fix compile warning
>
> That "V2" should be after the ---, but in any case:
>
> > --- a/net/mac80211/tx.c
> > +++ b/net/mac80211/tx.c
> > @@ -2728,6 +2728,7 @@ ieee80211_get_buffered_bc(struct ieee80211_hw *hw,
> > struct ps_data *ps;
> > struct ieee80211_tx_info *info;
> > struct ieee80211_chanctx_conf *chanctx_conf;
> > + struct ieee80211_sub_if_data *frame_sdata;
>
> There's already an sdata variable, why not write *sdata, *frame_sdata?
Actually you could even just use it since it's not needed after getting
the "ps" pointer.
johannes
next prev parent reply other threads:[~2013-02-12 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 16:37 [PATCHv2 0/1] mac80211: fix VLAN support on AP with ps-sta Michael Braun
2013-02-12 16:37 ` [PATCHv2 1/1] mac80211: fix WPA with VLAN on AP side " Michael Braun
2013-02-12 16:38 ` Johannes Berg
2013-02-12 16:40 ` Johannes Berg [this message]
2013-02-12 17:42 ` michael-dev
2013-02-12 17:45 ` Johannes Berg
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=1360687205.29913.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michael-dev@fami-braun.de \
--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