summaryrefslogtreecommitdiffstats
path: root/fs/cramfs
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2015-06-09 21:35:44 +0200
committerDavid S. Miller <davem@davemloft.net>2015-06-09 13:54:58 -0700
commit9c5a18a31b321f120efda412281bb9f610f84aa0 (patch)
tree25d00d5a3fa6e490148e4be8830b174361bd06dc /fs/cramfs
parent5879ae5fd052a63d5ac0684320cb7df3e83da7de (diff)
downloadlinux-9c5a18a31b321f120efda412281bb9f610f84aa0.tar.gz
linux-9c5a18a31b321f120efda412281bb9f610f84aa0.tar.bz2
linux-9c5a18a31b321f120efda412281bb9f610f84aa0.zip
cfg80211: wext: clear sinfo struct before calling driver
Until recently, mac80211 overwrote all the statistics it could provide when getting called, but it now relies on the struct having been zeroed by the caller. This was always the case in nl80211, but wext used a static struct which could even cause values from one device leak to another. Using a static struct is OK (as even documented in a comment) since the whole usage of this function and its return value is always locked under RTNL. Not clearing the struct for calling the driver has always been wrong though, since drivers were free to only fill values they could report, so calling this for one device and then for another would always have leaked values from one to the other. Fix this by initializing the structure in question before the driver method call. This fixes https://bugzilla.kernel.org/show_bug.cgi?id=99691 Cc: stable@vger.kernel.org Reported-by: Gerrit Renker <gerrit@erg.abdn.ac.uk> Reported-by: Alexander Kaltsas <alexkaltsas@gmail.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/cramfs')
0 files changed, 0 insertions, 0 deletions