From: Jakub Kicinski <kuba@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: "Denis V. Lunev" <den@virtuozzo.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, edumazet@google.com
Subject: Re: [PATCH -next] net: neigh: use dev_kfree_skb_irq instead of kfree_skb()
Date: Thu, 18 Aug 2022 09:32:24 -0700 [thread overview]
Message-ID: <20220818093224.2539d0bc@kernel.org> (raw)
In-Reply-To: <79784952-0d15-8a4a-aa8d-590bc243ab5e@virtuozzo.com>
Please put [PATCH net] as the tag for v2, this is a fix, not -next
material.
On Thu, 18 Aug 2022 11:00:13 +0200 Denis V. Lunev wrote:
> unsigned long flags;
> struct sk_buff *skb;
> + struct sk_buff_head tmp;
reverse xmas tree, so tmp should be declared before the shorter lines
> + 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);
while at it let's add an empty line here
> 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) {
No need to compare pointers to NULL
> + dev_put(skb->dev);
> + kfree_skb(skb);
> + }
next prev parent reply other threads:[~2022-08-18 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 4:37 [PATCH -next] net: neigh: use dev_kfree_skb_irq instead of kfree_skb() Yang Yingliang
2022-08-18 9:00 ` Denis V. Lunev
2022-08-18 10:47 ` Yang Yingliang
2022-08-18 16:32 ` Jakub Kicinski [this message]
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=20220818093224.2539d0bc@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=den@virtuozzo.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).