summaryrefslogtreecommitdiff
path: root/drivers/cpufreq
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2014-07-30 14:55:26 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-10-09 12:18:43 -0700
commit7dd311128022551d7876b26b7193157883494cd3 (patch)
treec650edc5bb6d5097ae7f33a0d3743a6abfa378e3 /drivers/cpufreq
parent6353c97aa7c7dd6b0c3fe717eeacb39e3873259e (diff)
downloadlinux-3.10-7dd311128022551d7876b26b7193157883494cd3.tar.gz
linux-3.10-7dd311128022551d7876b26b7193157883494cd3.tar.bz2
linux-3.10-7dd311128022551d7876b26b7193157883494cd3.zip
nl80211: clear skb cb before passing to netlink
commit bd8c78e78d5011d8111bc2533ee73b13a3bd6c42 upstream. In testmode and vendor command reply/event SKBs we use the skb cb data to store nl80211 parameters between allocation and sending. This causes the code for CONFIG_NETLINK_MMAP to get confused, because it takes ownership of the skb cb data when the SKB is handed off to netlink, and it doesn't explicitly clear it. Clear the skb cb explicitly when we're done and before it gets passed to netlink to avoid this issue. Reported-by: Assaf Azulay <assaf.azulay@intel.com> Reported-by: David Spinadel <david.spinadel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions