From: menglong8.dong@gmail.com
To: dsahern@kernel.org, kuba@kernel.org
Cc: rostedt@goodmis.org, mingo@redhat.com, xeb@mail.ru,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
imagedong@tencent.com, edumazet@google.com, kafai@fb.com,
talalahmad@google.com, keescook@chromium.org, alobakin@pm.me,
flyingpeng@tencent.com, mengensun@tencent.com,
dongli.zhang@oracle.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH net-next 0/3] net: gre: add skb drop reasons to gre packet receive
Date: Mon, 14 Mar 2022 21:33:09 +0800 [thread overview]
Message-ID: <20220314133312.336653-1-imagedong@tencent.com> (raw)
From: Menglong Dong <imagedong@tencent.com>
In the commit c504e5c2f964 ("net: skb: introduce kfree_skb_reason()"),
we added the support of reporting the reasons of skb drops to kfree_skb
tracepoint. And in this series patches, reasons for skb drops are added
to gre packet receiving path.
gre_rcv() in gre_demux.c is handled in the 1th patch.
In order to report skb drop reasons, we make erspan_rcv() return
PACKET_NEXT when no tunnel device found in the 2th patch. This may don't
correspond to 'PACKET_NEXT', but don't matter.
And gre_rcv() in ip_gre.c is handled in the 3th patch.
Following drop reasons are added(what they mean can be see in the
document for them):
SKB_DROP_REASON_GRE_VERSION
SKB_DROP_REASON_GRE_NOHANDLER
SKB_DROP_REASON_GRE_CSUM
SKB_DROP_REASON_GRE_NOTUNNEL
Maybe SKB_DROP_REASON_GRE_NOHANDLER can be replaced with
SKB_DROP_REASON_GRE_VERSION? As no gre_protocol found means that gre
version not supported.
PS: This set is parallel with the set "net: icmp: add skb drop reasons
to icmp", please don't mind :)
Menglong Dong (3):
net: gre_demux: add skb drop reasons to gre_rcv()
net: ipgre: make erspan_rcv() return PACKET_NEXT
net: ipgre: add skb drop reasons to gre_rcv()
include/linux/skbuff.h | 6 ++++++
include/trace/events/skb.h | 4 ++++
net/ipv4/gre_demux.c | 12 +++++++++---
net/ipv4/ip_gre.c | 30 +++++++++++++++++++-----------
4 files changed, 38 insertions(+), 14 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-14 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 13:33 menglong8.dong [this message]
2022-03-14 13:33 ` [PATCH net-next 1/3] net: gre_demux: add skb drop reasons to gre_rcv() menglong8.dong
2022-03-16 3:08 ` Jakub Kicinski
2022-03-16 3:49 ` David Ahern
2022-03-16 4:53 ` Menglong Dong
2022-03-16 14:45 ` David Ahern
2022-03-16 4:55 ` Jakub Kicinski
2022-03-16 10:12 ` David Laight
2022-03-16 18:55 ` Jakub Kicinski
2022-03-16 14:56 ` David Ahern
2022-03-16 18:57 ` Jakub Kicinski
2022-03-16 21:05 ` David Ahern
2022-03-16 4:41 ` Menglong Dong
2022-03-16 4:50 ` Jakub Kicinski
2022-03-14 13:33 ` [PATCH net-next 2/3] net: ipgre: make erspan_rcv() return PACKET_NEXT menglong8.dong
2022-03-14 13:33 ` [PATCH net-next 3/3] net: ipgre: add skb drop reasons to gre_rcv() menglong8.dong
2022-03-16 3:17 ` Jakub Kicinski
2022-03-16 6:21 ` Menglong Dong
2022-03-16 18:50 ` Jakub Kicinski
2022-03-16 18:51 ` 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=20220314133312.336653-1-imagedong@tencent.com \
--to=menglong8.dong@gmail.com \
--cc=alobakin@pm.me \
--cc=davem@davemloft.net \
--cc=dongli.zhang@oracle.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=flyingpeng@tencent.com \
--cc=imagedong@tencent.com \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengensun@tencent.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=talalahmad@google.com \
--cc=xeb@mail.ru \
--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®