From: Yang Yingliang <yangyingliang@huawei.com>
To: "Denis V. Lunev" <den@virtuozzo.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>
Subject: Re: [PATCH -next] net: neigh: use dev_kfree_skb_irq instead of kfree_skb()
Date: Thu, 18 Aug 2022 18:47:31 +0800 [thread overview]
Message-ID: <705de4aa-91bf-c559-419c-2bfd083c9067@huawei.com> (raw)
In-Reply-To: <79784952-0d15-8a4a-aa8d-590bc243ab5e@virtuozzo.com>
Hi,
On 2022/8/18 17:00, Denis V. Lunev wrote:
> On 18.08.2022 06:37, 'Yang Yingliang' via den wrote:
>> It is not allowed to call kfree_skb() from hardware interrupt
>> context or with interrupts being disabled. So replace kfree_skb()
>> with dev_kfree_skb_irq() under spin_lock_irqsave().
>>
>> Fixes: 66ba215cb513 ("neigh: fix possible DoS due to net iface
>> start/stop loop")
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>> net/core/neighbour.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
>> index 5b669eb80270..167826200f3e 100644
>> --- a/net/core/neighbour.c
>> +++ b/net/core/neighbour.c
>> @@ -328,7 +328,7 @@ static void pneigh_queue_purge(struct
>> sk_buff_head *list, struct net *net)
>> __skb_unlink(skb, list);
>> dev_put(dev);
>> - kfree_skb(skb);
>> + dev_kfree_skb_irq(skb);
>> }
>> skb = skb_next;
>> }
>
> Technically this is pretty much correct, but would it be better to
> move all skb to purge into the new list and after that purge
> them at once?
>
> what about something like this?
>
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index aa16a8017c5e..f7e30daa46ae 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -311,6 +311,9 @@ static void pneigh_queue_purge(struct sk_buff_head
> *list, struct net *net)
> {
> unsigned long flags;
> struct sk_buff *skb;
> + struct sk_buff_head tmp;
> +
> + skb_queue_head_init(&tmp);
>
> spin_lock_irqsave(&list->lock, flags);
> skb = skb_peek(list);
> @@ -318,12 +321,16 @@ static void pneigh_queue_purge(struct
> sk_buff_head *list, struct net *net)
> struct sk_buff *skb_next = skb_peek_next(skb, list);
> if (net == NULL || net == dev_net(skb->dev)) {
> __skb_unlink(skb, list);
> - dev_put(skb->dev);
> - kfree_skb(skb);
> + __skb_queue_tail(&tmp, skb);
> }
> skb = skb_next;
> } while (skb != NULL);
> spin_unlock_irqrestore(&list->lock, flags);
> +
> + while ((skb = __skb_dequeue(&tmp)) != NULL) {
> + dev_put(skb->dev);
> + kfree_skb(skb);
> + }
> }
It's better, I can send a v2 later.
Thanks,
Yang
>
> iris ~/src/linux-2.6 $
>
> .
next prev parent reply other threads:[~2022-08-18 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 4:37 Yang Yingliang
2022-08-18 9:00 ` Denis V. Lunev
2022-08-18 10:47 ` Yang Yingliang [this message]
2022-08-18 16:32 ` Jakub Kicinski
2022-08-19 1:44 ` Yang Yingliang
2022-08-19 2:39 ` 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=705de4aa-91bf-c559-419c-2bfd083c9067@huawei.com \
--to=yangyingliang@huawei.com \
--cc=davem@davemloft.net \
--cc=den@virtuozzo.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®