summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2012-01-19 16:20:57 (GMT)
committerJohn W. Linville <linville@tuxdriver.com>2012-01-24 19:47:10 (GMT)
commitb49ba04a3a0382e7314d990707c21094c410425a (patch)
treedc510fd3cf007d838881539b0a1fab0b92ef2555 /init
parent405385f8ce7a2ed8f82e216d88b5282142e1288b (diff)
downloadlinux-b49ba04a3a0382e7314d990707c21094c410425a.tar.xz
iwlwifi: fix PCI-E transport "inta" race
When an interrupt comes in, we read the reason bits and collect them into "trans_pcie->inta". This happens with the spinlock held. However, there's a bug resetting this variable -- that happens after the spinlock has been released. This means that it is possible for interrupts to be missed if the reset happens after some other interrupt reasons were already added to the variable. I found this by code inspection, looking for a reason that we sometimes see random commands time out. It seems possible that this causes such behaviour, but I can't say for sure right now since it happens extremely infrequently on my test systems. Cc: stable@vger.kernel.org [3.2] Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions