summaryrefslogtreecommitdiff
path: root/Kconfig
diff options
context:
space:
mode:
authorEmmanuel Grumbach <emmanuel.grumbach@intel.com>2012-07-04 13:59:08 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-07-19 08:58:57 -0700
commit1214b7852425b78a2b73b0a759ec55210340396d (patch)
tree13a5b867d8d34fde6cbe9f5ff8a0ed6f127bb090 /Kconfig
parent57cff816121720c80b39e3b3fb0ef36128fdc45b (diff)
downloadlwn-1214b7852425b78a2b73b0a759ec55210340396d.tar.gz
lwn-1214b7852425b78a2b73b0a759ec55210340396d.zip
iwlegacy: don't mess up the SCD when removing a key
commit b48d96652626b315229b1b82c6270eead6a77a6d upstream. When we remove a key, we put a key index which was supposed to tell the fw that we are actually removing the key. But instead the fw took that index as a valid index and messed up the SRAM of the device. This memory corruption on the device mangled the data of the SCD. The impact on the user is that SCD queue 2 got stuck after having removed keys. Reported-by: Paul Bolle <pebolle@tiscali.nl> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions