summaryrefslogtreecommitdiff
path: root/arch/xtensa
diff options
context:
space:
mode:
authorEmmanuel Grumbach <emmanuel.grumbach@intel.com>2018-12-03 21:16:07 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-12-13 09:21:37 +0100
commitd1deb58639b05e14b5dd859f587edc628aa4f4e0 (patch)
treef00b9959c09141b2a154abd926fb6bbba5c5ae55 /arch/xtensa
parent5a7b2af0c7ec872ffd4b0b87e4f102108e112af0 (diff)
mac80211: ignore NullFunc frames in the duplicate detection
commit 990d71846a0b7281bd933c34d734e6afc7408e7e upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/xtensa')
0 files changed, 0 insertions, 0 deletions