summaryrefslogtreecommitdiffstats
path: root/arch/sparc/mm/srmmu.c
diff options
context:
space:
mode:
authorEmmanuel Grumbach <emmanuel.grumbach@intel.com>2012-07-04 13:59:08 +0200
committerJohn W. Linville <linville@tuxdriver.com>2012-07-09 15:01:03 -0400
commitb48d96652626b315229b1b82c6270eead6a77a6d (patch)
treebc2bff971eeb48d25c3398c0af586da62e395bb2 /arch/sparc/mm/srmmu.c
parentc2ca7d92ed4bbd779516beb6eb226e19f7f7ab0f (diff)
downloadblackbird-op-linux-b48d96652626b315229b1b82c6270eead6a77a6d.tar.gz
blackbird-op-linux-b48d96652626b315229b1b82c6270eead6a77a6d.zip
iwlegacy: don't mess up the SCD when removing a key
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> Cc: stable@vger.kernel.org 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>
Diffstat (limited to 'arch/sparc/mm/srmmu.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud