From: Roman Mashak <mrv@mojatatu.com>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
David Miller <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Menglong Dong <imagedong@tencent.com>,
Eric Dumazet <edumazet@google.com>,
Alexander Lobakin <alobakin@pm.me>,
Cong Wang <cong.wang@bytedance.com>,
paulb@nvidia.com, Talal Ahmad <talalahmad@google.com>,
Kees Cook <keescook@chromium.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
flyingpeng@tencent.com, Mengen Sun <mengensun@tencent.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Yajun Deng <yajun.deng@linux.dev>,
Roopa Prabhu <roopa@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/3] net: ip: add skb drop reasons for ip egress path
Date: Fri, 25 Feb 2022 08:41:28 -0500 [thread overview]
Message-ID: <85v8x3xdvb.fsf@mojatatu.com> (raw)
In-Reply-To: <CADxym3apww2XEeTX=kU7gW5mbQ9STwVyQypK4Xbsmgid9s+2og@mail.gmail.com> (Menglong Dong's message of "Fri, 25 Feb 2022 14:05:08 +0800")
Menglong Dong <menglong8.dong@gmail.com> writes:
> On Tue, Feb 22, 2022 at 11:13 AM David Ahern <dsahern@kernel.org> wrote:
>>
>> On 2/20/22 8:57 AM, menglong8.dong@gmail.com wrote:
>> > From: Menglong Dong <imagedong@tencent.com>
>> >
>> > Replace kfree_skb() with kfree_skb_reason() in the packet egress path of
>> > IP layer (both IPv4 and IPv6 are considered).
>> >
>> > Following functions are involved:
>> >
>> > __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
Is this a typo and should be SKB_DROP_REASON_IPV6DISABLED ?
[...]
next prev parent reply other threads:[~2022-02-25 13:42 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 [this message]
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
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=85v8x3xdvb.fsf@mojatatu.com \
--to=mrv@mojatatu.com \
--cc=alobakin@pm.me \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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
all inboxes | Powered by JetHome®