From: David Ahern <dsahern@kernel.org>
To: menglong8.dong@gmail.com
Cc: rostedt@goodmis.org, mingo@redhat.com, davem@davemloft.net,
kuba@kernel.org, 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 v2 1/3] net: ip: add skb drop reasons for ip egress path
Date: Fri, 25 Feb 2022 08:42:51 -0700 [thread overview]
Message-ID: <d5be0cf8-0607-5448-e235-183980f8f44a@kernel.org> (raw)
In-Reply-To: <20220225071739.1956657-2-imagedong@tencent.com>
On 2/25/22 12:17 AM, menglong8.dong@gmail.com wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> Replace kfree_skb() which is used in the packet egress path of IP layer
> with kfree_skb_reason(). Functions that are involved include:
>
> __ip_queue_xmit()
> ip_finish_output()
> ip_mc_finish_output()
> ip6_output()
> ip6_finish_output()
> ip6_finish_output2()
>
> Following new drop reasons are introduced:
>
> SKB_DROP_REASON_IP_OUTNOROUTES
> SKB_DROP_REASON_BPF_CGROUP_EGRESS
> SKB_DROP_REASON_IPV6DSIABLED
A new version is needed to fix the typo Roman noticed; logic wise:
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2022-02-25 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 7:17 [PATCH net-next v2 0/3] net: use kfree_skb_reason() for ip/neighbour menglong8.dong
2022-02-25 7:17 ` [PATCH net-next v2 1/3] net: ip: add skb drop reasons for ip egress path menglong8.dong
2022-02-25 15:42 ` David Ahern [this message]
2022-02-25 7:17 ` [PATCH net-next v2 2/3] net: neigh: use kfree_skb_reason() for __neigh_event_send() menglong8.dong
2022-02-25 15:39 ` David Ahern
2022-02-25 7:17 ` [PATCH net-next v2 3/3] net: neigh: add skb drop reasons to arp_error_report() menglong8.dong
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=d5be0cf8-0607-5448-e235-183980f8f44a@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