All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: menglong8.dong@gmail.com, rostedt@goodmis.org, dsahern@kernel.org
Cc: mingo@redhat.com, davem@davemloft.net, kuba@kernel.org,
	nhorman@tuxdriver.com, edumazet@google.com,
	yoshfuji@linux-ipv6.org, jonathan.lemon@gmail.com,
	alobakin@pm.me, cong.wang@bytedance.com, pabeni@redhat.com,
	talalahmad@google.com, haokexin@gmail.com, keescook@chromium.org,
	imagedong@tencent.com, atenart@kernel.org, bigeasy@linutronix.de,
	weiwan@google.com, arnd@arndb.de, vvs@virtuozzo.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: skb: use kfree_skb_with_reason() in tcp_v4_rcv()
Date: Wed, 29 Dec 2021 13:18:36 -0700	[thread overview]
Message-ID: <c3582b56-905c-b6bf-e92e-e6d81ae9f2e0@gmail.com> (raw)
In-Reply-To: <20211229143205.410731-3-imagedong@tencent.com>

On 12/29/21 7:32 AM, menglong8.dong@gmail.com wrote:
> From: Menglong Dong <imagedong@tencent.com>
> 
> Replace kfree_skb() with kfree_skb_with_reason() in tcp_v4_rcv().
> Following drop reason are added:
> 
> SKB_DROP_REASON_NO_SOCK
> SKB_DROP_REASON_BAD_PACKET
> SKB_DROP_REASON_TCP_CSUM
> 
> After this patch, 'kfree_skb' event will print message like this:
> 
> $           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
> $              | |         |   |||||     |         |
>           <idle>-0       [000] ..s1.    36.113438: kfree_skb: skbaddr=(____ptrval____) protocol=2048 location=(____ptrval____) reason: NO_SOCK
> 
> The reason of skb drop is printed too.
> 
> Signed-off-by: Menglong Dong <imagedong@tencent.com>
> ---
>  include/linux/skbuff.h     |  3 +++
>  include/trace/events/skb.h |  3 +++
>  net/ipv4/tcp_ipv4.c        | 10 ++++++++--

your first patch set was targeting UDP and now you are starting with tcp?


>  3 files changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 3620b3ff2154..f85db6c035d1 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -313,6 +313,9 @@ struct sk_buff;
>   */
>  enum skb_drop_reason {
>  	SKB_DROP_REASON_NOT_SPECIFIED,
> +	SKB_DROP_REASON_NO_SOCK,

SKB_DROP_REASON_NO_SOCKET

> +	SKB_DROP_REASON_BAD_PACKET,

SKB_DROP_REASON_PKT_TOO_SMALL

User oriented messages, not code based.


> +	SKB_DROP_REASON_TCP_CSUM,
>  	SKB_DROP_REASON_MAX,
>  };
>  
> diff --git a/include/trace/events/skb.h b/include/trace/events/skb.h
> index cab1c08a30cd..b9ea6b4ed7ec 100644
> --- a/include/trace/events/skb.h
> +++ b/include/trace/events/skb.h
> @@ -11,6 +11,9 @@
>  
>  #define TRACE_SKB_DROP_REASON					\
>  	EM(SKB_DROP_REASON_NOT_SPECIFIED, NOT_SPECIFIED)	\
> +	EM(SKB_DROP_REASON_NO_SOCK, NO_SOCK)			\
> +	EM(SKB_DROP_REASON_BAD_PACKET, BAD_PACKET)		\
> +	EM(SKB_DROP_REASON_TCP_CSUM, TCP_CSUM)			\
>  	EMe(SKB_DROP_REASON_MAX, HAHA_MAX)
>  
>  #undef EM
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index ac10e4cdd8d0..03dc4c79b84b 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -1971,8 +1971,10 @@ int tcp_v4_rcv(struct sk_buff *skb)
>  	const struct tcphdr *th;
>  	bool refcounted;
>  	struct sock *sk;
> +	int drop_reason;
>  	int ret;
>  
> +	drop_reason = 0;

	drop_reason = SKB_DROP_REASON_NOT_SPECIFIED;


  reply	other threads:[~2021-12-29 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 14:32 [PATCH net-next 0/2] net: skb: introduce kfree_skb_with_reason() menglong8.dong
2021-12-29 14:32 ` [PATCH net-next 1/2] " menglong8.dong
2021-12-29 14:32 ` [PATCH net-next 2/2] net: skb: use kfree_skb_with_reason() in tcp_v4_rcv() menglong8.dong
2021-12-29 20:18   ` David Ahern [this message]
2021-12-30  2:36     ` Menglong 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=c3582b56-905c-b6bf-e92e-e6d81ae9f2e0@gmail.com \
    --to=dsahern@gmail.com \
    --cc=alobakin@pm.me \
    --cc=arnd@arndb.de \
    --cc=atenart@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=cong.wang@bytedance.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=haokexin@gmail.com \
    --cc=imagedong@tencent.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menglong8.dong@gmail.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=talalahmad@google.com \
    --cc=vvs@virtuozzo.com \
    --cc=weiwan@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.