diff options
author | Johannes Berg <johannes.berg@intel.com> | 2011-07-07 18:45:03 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2011-07-08 11:42:21 -0400 |
commit | 9e26297a56453315ae6829aec609b5a6309af7b4 (patch) | |
tree | 9152708917200d9b4f0ecc027c13c5da836f22e7 /net/socket.c | |
parent | 1d738e64f3d957d56c1b51e64ebdef986a8760e3 (diff) | |
download | kernel_goldelico_gta04-9e26297a56453315ae6829aec609b5a6309af7b4.zip kernel_goldelico_gta04-9e26297a56453315ae6829aec609b5a6309af7b4.tar.gz kernel_goldelico_gta04-9e26297a56453315ae6829aec609b5a6309af7b4.tar.bz2 |
mac80211: simplify RX PN/IV handling
The current rx->queue value is slightly confusing.
It is set to 16 on non-QoS frames, including data,
and then used for sequence number and PN/IV checks.
Until recently, we had a TKIP IV checking bug that
had been introduced in 2008 to fix a seqno issue.
Before that, we always used TID 0 for checking the
PN or IV on non-QoS packets.
Go back to the old status for PN/IV checks using
the TID 0 counter for non-QoS by splitting up the
rx->queue value into "seqno_idx" and "security_idx"
in order to avoid confusion in the future. They
each have special rules on the value used for non-
QoS data frames.
Since the handling is now unified, also revert the
special TKIP handling from my patch
"mac80211: fix TKIP replay vulnerability".
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/socket.c')
0 files changed, 0 insertions, 0 deletions