[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211229143205.410731-1-imagedong@tencent.com>
Date: Wed, 29 Dec 2021 22:32:03 +0800
From: menglong8.dong@...il.com
To: rostedt@...dmis.org, dsahern@...nel.org
Cc: mingo@...hat.com, davem@...emloft.net, kuba@...nel.org,
nhorman@...driver.com, edumazet@...gle.com,
yoshfuji@...ux-ipv6.org, jonathan.lemon@...il.com, alobakin@...me,
cong.wang@...edance.com, pabeni@...hat.com, talalahmad@...gle.com,
haokexin@...il.com, keescook@...omium.org, imagedong@...cent.com,
atenart@...nel.org, bigeasy@...utronix.de, weiwan@...gle.com,
arnd@...db.de, vvs@...tuozzo.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: [PATCH net-next 0/2] net: skb: introduce kfree_skb_with_reason()
From: Menglong Dong <imagedong@...cent.com>
In this series patch, the interface kfree_skb_with_reason() is
introduced(), which is used to collect skb drop reason, and pass
it to 'kfree_skb' tracepoint. Therefor, 'drop_monitor' or eBPF is
able to monitor abnormal skb with detail reason.
In fact, this series patches are out of the intelligence of David
and Steve, I'm just a truck man :/
Previous discussion is here:
https://lore.kernel.org/netdev/20211118105752.1d46e990@gandalf.local.home/
https://lore.kernel.org/netdev/67b36bd8-2477-88ac-83a0-35a1eeaf40c9@gmail.com/
In the first patch, kfree_skb_with_reason() is introduced and
the 'reason' field is added to 'kfree_skb' tracepoint. In the
second patch, 'kfree_skb()' in replaced with 'kfree_skb_with_reason()'
in tcp_v4_rcv().
Menglong Dong (2):
net: skb: introduce kfree_skb_with_reason()
net: skb: use kfree_skb_with_reason() in tcp_v4_rcv()
include/linux/skbuff.h | 16 ++++++++++++++++
include/trace/events/skb.h | 39 +++++++++++++++++++++++++++++++-------
net/core/dev.c | 3 ++-
net/core/drop_monitor.c | 10 +++++++---
net/core/skbuff.c | 22 ++++++++++++++++++++-
net/ipv4/tcp_ipv4.c | 10 ++++++++--
6 files changed, 86 insertions(+), 14 deletions(-)
--
2.27.0
Powered by blists - more mailing lists