net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ context
authorFuqian Huang <huangfq.daxian@gmail.com>
Fri, 9 Aug 2019 05:35:39 +0000 (13:35 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 10 Sep 2019 09:30:59 +0000 (10:30 +0100)
commit2046ecf3e1703839df5caa9c44afbf484bcd3622
tree8b98c34dee7ba4ec863c0369eca8fe0f52631644
parentbf489db05ebf7106dd77f79e6edabc45fc318416
net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ context

[ Upstream commit 8c25d0887a8bd0e1ca2074ac0c6dff173787a83b ]

As spin_unlock_irq will enable interrupts.
Function tsi108_stat_carry is called from interrupt handler tsi108_irq.
Interrupts are enabled in interrupt handler.
Use spin_lock_irqsave/spin_unlock_irqrestore instead of spin_(un)lock_irq
in IRQ context to avoid this.

Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/net/ethernet/tundra/tsi108_eth.c