From: Leon Romanovsky <leon@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2 1/2] net: apple: mace: don't call dev_kfree_skb() under spin_lock_irqsave()
Date: Thu, 8 Dec 2022 09:58:31 +0200 [thread overview]
Message-ID: <Y5GZJ2rBuMZoZ0e7@unreal> (raw)
In-Reply-To: <20221207012959.2800421-1-yangyingliang@huawei.com>
On Wed, Dec 07, 2022 at 09:29:58AM +0800, Yang Yingliang wrote:
> It is not allowed to call consume_skb() from hardware interrupt context
> or with interrupts being disabled. So replace dev_kfree_skb() with
> dev_consume_skb_irq() under spin_lock_irqsave().
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> v1 -> v2:
> Add a fix tag.
> ---
> drivers/net/ethernet/apple/mace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/apple/mace.c b/drivers/net/ethernet/apple/mace.c
> index d0a771b65e88..77b4ed05140b 100644
> --- a/drivers/net/ethernet/apple/mace.c
> +++ b/drivers/net/ethernet/apple/mace.c
> @@ -846,7 +846,7 @@ static void mace_tx_timeout(struct timer_list *t)
> if (mp->tx_bad_runt) {
> mp->tx_bad_runt = 0;
> } else if (i != mp->tx_fill) {
> - dev_kfree_skb(mp->tx_bufs[i]);
> + dev_consume_skb_irq(mp->tx_bufs[i]);
Same question, why did you chose dev_consume_skb_irq and not dev_kfree_skb_irq?
Thanks
> if (++i >= N_TX_RING)
> i = 0;
> mp->tx_empty = i;
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-12-08 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 1:29 [PATCH net v2 1/2] net: apple: mace: don't call dev_kfree_skb() under spin_lock_irqsave() Yang Yingliang
2022-12-07 1:29 ` [PATCH net v2 2/2] net: apple: bmac: " Yang Yingliang
2022-12-08 7:58 ` Leon Romanovsky [this message]
2022-12-08 8:39 ` [PATCH net v2 1/2] net: apple: mace: " Yang Yingliang
2022-12-08 16:33 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5GZJ2rBuMZoZ0e7@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangyingliang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox