From: David Ahern <dsahern@kernel.org>
To: menglong8.dong@gmail.com, kuba@kernel.org
Cc: rostedt@goodmis.org, mingo@redhat.com, davem@davemloft.net,
yoshfuji@linux-ipv6.org, imagedong@tencent.com,
edumazet@google.com, alobakin@pm.me, cong.wang@bytedance.com,
paulb@nvidia.com, talalahmad@google.com, keescook@chromium.org,
ilias.apalodimas@linaro.org, memxor@gmail.com,
flyingpeng@tencent.com, mengensun@tencent.com,
daniel@iogearbox.net, yajun.deng@linux.dev, roopa@nvidia.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] net: neigh: use kfree_skb_reason() for __neigh_event_send()
Date: Mon, 21 Feb 2022 20:17:01 -0700 [thread overview]
Message-ID: <2969b15c-b825-3b0e-2ad7-00633ee6815b@kernel.org> (raw)
In-Reply-To: <20220220155705.194266-3-imagedong@tencent.com>
On 2/20/22 8:57 AM, menglong8.dong@gmail.com wrote:
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index c310a4a8fc86..206b66f5ce6b 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -393,6 +393,15 @@ enum skb_drop_reason {
> * see the doc for disable_ipv6
> * in ip-sysctl.rst for detail
> */
> + SKB_DROP_REASON_NEIGH_FAILED, /* dropped as the state of
> + * neighbour is NUD_FAILED
> + */
/* neigh entry in failed state */
> + SKB_DROP_REASON_NEIGH_QUEUEFULL, /* the skbs that waiting
> + * for sending on the queue
> + * of neigh->arp_queue is
> + * full, and the skbs on the
> + * tail will be dropped
> + */
/* arp_queue for neigh entry is full */
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index ec0bf737b076..c353834e8fa9 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -1171,7 +1171,7 @@ int __neigh_event_send(struct neighbour *neigh, struct sk_buff *skb,
> neigh->updated = jiffies;
> write_unlock_bh(&neigh->lock);
>
> - kfree_skb(skb);
> + kfree_skb_reason(skb, SKB_DROP_REASON_NEIGH_FAILED);
> return 1;
> }
> } else if (neigh->nud_state & NUD_STALE) {
> @@ -1193,7 +1193,7 @@ int __neigh_event_send(struct neighbour *neigh, struct sk_buff *skb,
> if (!buff)
> break;
> neigh->arp_queue_len_bytes -= buff->truesize;
> - kfree_skb(buff);
> + kfree_skb_reason(buff, SKB_DROP_REASON_NEIGH_QUEUEFULL);
> NEIGH_CACHE_STAT_INC(neigh->tbl, unres_discards);
> }
> skb_dst_force(skb);
what about out_dead: path? the tracepoint there shows that path is of
interest.
next prev parent reply other threads:[~2022-02-22 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 15:57 [PATCH net-next 0/3] net: use kfree_skb_reason() for ip/neighbour menglong8.dong
2022-02-20 15:57 ` [PATCH net-next 1/3] net: ip: add skb drop reasons for ip egress path menglong8.dong
2022-02-22 3:13 ` David Ahern
2022-02-22 3:44 ` Menglong Dong
2022-02-25 6:05 ` Menglong Dong
2022-02-25 13:41 ` Roman Mashak
2022-02-25 13:53 ` Menglong Dong
2022-02-20 15:57 ` [PATCH net-next 2/3] net: neigh: use kfree_skb_reason() for __neigh_event_send() menglong8.dong
2022-02-22 3:17 ` David Ahern [this message]
2022-02-22 3:47 ` Menglong Dong
2022-02-20 15:57 ` [PATCH net-next 3/3] net: neigh: add skb drop reasons to arp_error_report() menglong8.dong
2022-02-22 3:19 ` David Ahern
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=2969b15c-b825-3b0e-2ad7-00633ee6815b@kernel.org \
--to=dsahern@kernel.org \
--cc=alobakin@pm.me \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=flyingpeng@tencent.com \
--cc=ilias.apalodimas@linaro.org \
--cc=imagedong@tencent.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=mengensun@tencent.com \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulb@nvidia.com \
--cc=roopa@nvidia.com \
--cc=rostedt@goodmis.org \
--cc=talalahmad@google.com \
--cc=yajun.deng@linux.dev \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).