summaryrefslogtreecommitdiffstats
path: root/net/can/af_can.h
diff options
context:
space:
mode:
authorEmmanuel Grumbach <emmanuel.grumbach@intel.com>2018-12-03 20:16:07 +0100
committerJohannes Berg <johannes.berg@intel.com>2018-12-05 12:34:49 +0100
commit990d71846a0b7281bd933c34d734e6afc7408e7e (patch)
tree2d6d7e5336f8da1035ca3d92fa14dc1d2abb8ba3 /net/can/af_can.h
parentmac80211: fix reordering of buffered broadcast packets (diff)
downloadlinux-990d71846a0b7281bd933c34d734e6afc7408e7e.tar.xz
linux-990d71846a0b7281bd933c34d734e6afc7408e7e.zip
mac80211: ignore NullFunc frames in the duplicate detection
NullFunc packets should never be duplicate just like QoS-NullFunc packets. We saw a client that enters / exits power save with NullFunc frames (and not with QoS-NullFunc) despite the fact that the association supports HT. This specific client also re-uses a non-zero sequence number for different NullFunc frames. At some point, the client had to send a retransmission of the NullFunc frame and we dropped it, leading to a misalignment in the power save state. Fix this by never consider a NullFunc frame as duplicate, just like we do for QoS NullFunc frames. This fixes https://bugzilla.kernel.org/show_bug.cgi?id=201449 CC: <stable@vger.kernel.org> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/can/af_can.h')
0 files changed, 0 insertions, 0 deletions