aboutsummaryrefslogtreecommitdiffstats
path: root/net/bridge/br_stp_timer.c
diff options
context:
space:
mode:
authorMugunthan V N <mugunthanvnm@ti.com>2013-05-02 01:52:11 +0000
committerDavid S. Miller <davem@davemloft.net>2013-05-02 16:52:04 -0400
commitaf5c6df704af46f2cfebea329887f3d70ccb7b3d (patch)
tree1c7a55c1c4f52644467bd29f57b0079d5e021434 /net/bridge/br_stp_timer.c
parentxen-netback: better names for thresholds (diff)
downloadlinux-dev-af5c6df704af46f2cfebea329887f3d70ccb7b3d.tar.xz
linux-dev-af5c6df704af46f2cfebea329887f3d70ccb7b3d.zip
drivers: net: cpsw: irq not disabled in cpsw isr in particular sequence
In CPSW NAPI, after processing all interrupts IRQ is enabled and then book keeping irq_enabled is updated. In random cases when a packet is transmitted or received between processing packets and IRQ enabled, then just after enabled IRQ and before irq_enabled is updated, ISR is called so IRQs are not disabled as irq_enabled is still false and CPU gets locked in CPSW ISR. By changing the sequence as update the irq_enabled and then enable IRQ fixes the issue. This issue is not captured always as it is a timing issue whether Tx or Rx IRQ is invoked between packet processing and enable IRQ. Cc: Sebastian Siewior <bigeasy@linutronix.de> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions