netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave()
@ 2022-12-08 12:01 Yang Yingliang
  2022-12-08 16:47 ` Jakub Kicinski
  2022-12-12  9:40 ` patchwork-bot+netdevbpf
  0 siblings, 2 replies; 4+ messages in thread
From: Yang Yingliang @ 2022-12-08 12:01 UTC (permalink / raw)
  To: netdev; +Cc: jdmason, davem, edumazet, kuba, pabeni, leon

It is not allowed to call kfree_skb() or consume_skb() from hardware
interrupt context or with hardware interrupts being disabled.

It should use dev_kfree_skb_irq() or dev_consume_skb_irq() instead.
The difference between them is free reason, dev_kfree_skb_irq() means
the SKB is dropped in error and dev_consume_skb_irq() means the SKB
is consumed in normal.

In this case, dev_kfree_skb() is called in free_tx_buffers() to drop
the SKBs in tx buffers, when the card is down, so replace it with
dev_kfree_skb_irq() here.

Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
v4 -> v3:
  Update commit message, and change to use dev_kfree_skb_irq().

v2 -> v3:
  Update commit message.

v1 -> v2:
  Add fix tag.
---
 drivers/net/ethernet/neterion/s2io.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/neterion/s2io.c b/drivers/net/ethernet/neterion/s2io.c
index 1d3c4474b7cb..a83d61d45936 100644
--- a/drivers/net/ethernet/neterion/s2io.c
+++ b/drivers/net/ethernet/neterion/s2io.c
@@ -2386,7 +2386,7 @@ static void free_tx_buffers(struct s2io_nic *nic)
 			skb = s2io_txdl_getskb(&mac_control->fifos[i], txdp, j);
 			if (skb) {
 				swstats->mem_freed += skb->truesize;
-				dev_kfree_skb(skb);
+				dev_kfree_skb_irq(skb);
 				cnt++;
 			}
 		}
-- 
2.25.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave()
  2022-12-08 12:01 [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave() Yang Yingliang
@ 2022-12-08 16:47 ` Jakub Kicinski
  2022-12-12  1:58   ` Yang Yingliang
  2022-12-12  9:40 ` patchwork-bot+netdevbpf
  1 sibling, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2022-12-08 16:47 UTC (permalink / raw)
  To: Yang Yingliang; +Cc: netdev, jdmason, davem, edumazet, pabeni, leon

On Thu, 8 Dec 2022 20:01:21 +0800 Yang Yingliang wrote:
> It is not allowed to call kfree_skb() or consume_skb() from hardware
> interrupt context or with hardware interrupts being disabled.
> 
> It should use dev_kfree_skb_irq() or dev_consume_skb_irq() instead.
> The difference between them is free reason, dev_kfree_skb_irq() means
> the SKB is dropped in error and dev_consume_skb_irq() means the SKB
> is consumed in normal.
> 
> In this case, dev_kfree_skb() is called in free_tx_buffers() to drop
> the SKBs in tx buffers, when the card is down, so replace it with
> dev_kfree_skb_irq() here.

Make sure you read this:

https://www.kernel.org/doc/html/next/process/maintainer-netdev.html

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave()
  2022-12-08 16:47 ` Jakub Kicinski
@ 2022-12-12  1:58   ` Yang Yingliang
  0 siblings, 0 replies; 4+ messages in thread
From: Yang Yingliang @ 2022-12-12  1:58 UTC (permalink / raw)
  To: Jakub Kicinski; +Cc: netdev, jdmason, davem, edumazet, pabeni, leon


On 2022/12/9 0:47, Jakub Kicinski wrote:
> On Thu, 8 Dec 2022 20:01:21 +0800 Yang Yingliang wrote:
>> It is not allowed to call kfree_skb() or consume_skb() from hardware
>> interrupt context or with hardware interrupts being disabled.
>>
>> It should use dev_kfree_skb_irq() or dev_consume_skb_irq() instead.
>> The difference between them is free reason, dev_kfree_skb_irq() means
>> the SKB is dropped in error and dev_consume_skb_irq() means the SKB
>> is consumed in normal.
>>
>> In this case, dev_kfree_skb() is called in free_tx_buffers() to drop
>> the SKBs in tx buffers, when the card is down, so replace it with
>> dev_kfree_skb_irq() here.
> Make sure you read this:
>
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
OK.

Thanks,
Yang
> .

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave()
  2022-12-08 12:01 [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave() Yang Yingliang
  2022-12-08 16:47 ` Jakub Kicinski
@ 2022-12-12  9:40 ` patchwork-bot+netdevbpf
  1 sibling, 0 replies; 4+ messages in thread
From: patchwork-bot+netdevbpf @ 2022-12-12  9:40 UTC (permalink / raw)
  To: Yang Yingliang; +Cc: netdev, jdmason, davem, edumazet, kuba, pabeni, leon

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 8 Dec 2022 20:01:21 +0800 you wrote:
> It is not allowed to call kfree_skb() or consume_skb() from hardware
> interrupt context or with hardware interrupts being disabled.
> 
> It should use dev_kfree_skb_irq() or dev_consume_skb_irq() instead.
> The difference between them is free reason, dev_kfree_skb_irq() means
> the SKB is dropped in error and dev_consume_skb_irq() means the SKB
> is consumed in normal.
> 
> [...]

Here is the summary with links:
  - [net,v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave()
    https://git.kernel.org/netdev/net/c/6cee96e09df5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-12-12  9:40 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-12-08 12:01 [PATCH net v4] ethernet: s2io: don't call dev_kfree_skb() under spin_lock_irqsave() Yang Yingliang
2022-12-08 16:47 ` Jakub Kicinski
2022-12-12  1:58   ` Yang Yingliang
2022-12-12  9:40 ` patchwork-bot+netdevbpf

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).