BPF List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: menglong8.dong@gmail.com, kuba@kernel.org
Cc: edumazet@google.com, davem@davemloft.net, rostedt@goodmis.org,
	mingo@redhat.com, yoshfuji@linux-ipv6.org, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	imagedong@tencent.com, talalahmad@google.com,
	keescook@chromium.org, ilias.apalodimas@linaro.org,
	alobakin@pm.me, memxor@gmail.com, atenart@kernel.org,
	bigeasy@linutronix.de, pabeni@redhat.com, linyunsheng@huawei.com,
	arnd@arndb.de, yajun.deng@linux.dev, roopa@nvidia.com,
	willemb@google.com, vvs@virtuozzo.com, cong.wang@bytedance.com,
	luiz.von.dentz@intel.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	flyingpeng@tencent.com
Subject: Re: [PATCH net-next v2 0/9] net: add skb drop reasons to TCP packet receive
Date: Fri, 18 Feb 2022 14:23:39 -0700	[thread overview]
Message-ID: <ac145b7b-8c78-88dd-ded5-c780bf7e94e1@kernel.org> (raw)
In-Reply-To: <20220218083133.18031-1-imagedong@tencent.com>

On 2/18/22 1:31 AM, menglong8.dong@gmail.com wrote:
> 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 TCP layer (both TCPv4 and TCPv6 are considered).
> Following functions are processed:
> 
> tcp_v4_rcv()
> tcp_v6_rcv()
> tcp_v4_inbound_md5_hash()
> tcp_v6_inbound_md5_hash()
> tcp_add_backlog()
> tcp_v4_do_rcv()
> tcp_v6_do_rcv()
> tcp_rcv_established()
> tcp_data_queue()
> tcp_data_queue_ofo()
> 
> The functions we handled are mostly for packet ingress, as skb drops
> hardly happens in the egress path of TCP layer. However, it's a little
> complex for TCP state processing, as I find that it's hard to report skb
> drop reasons to where it is freed. For example, when skb is dropped in
> tcp_rcv_state_process(), the reason can be caused by the call of
> tcp_v4_conn_request(), and it's hard to return a drop reason from
> tcp_v4_conn_request(). So such cases are skipped  for this moment.
> 
> Following new drop reasons are introduced (what they mean can be see
> in the document for them):
> 
> /* SKB_DROP_REASON_TCP_MD5* corresponding to LINUX_MIB_TCPMD5* */
> SKB_DROP_REASON_TCP_MD5NOTFOUND
> SKB_DROP_REASON_TCP_MD5UNEXPECTED
> SKB_DROP_REASON_TCP_MD5FAILURE
> SKB_DROP_REASON_SOCKET_BACKLOG
> SKB_DROP_REASON_TCP_FLAGS
> SKB_DROP_REASON_TCP_ZEROWINDOW
> SKB_DROP_REASON_TCP_OLD_DATA
> SKB_DROP_REASON_TCP_OVERWINDOW
> /* corresponding to LINUX_MIB_TCPOFOMERGE */
> SKB_DROP_REASON_TCP_OFOMERGE
> 
> Here is a example to get TCP packet drop reasons from ftrace:
> 
> $ echo 1 > /sys/kernel/debug/tracing/events/skb/kfree_skb/enable
> $ cat /sys/kernel/debug/tracing/trace
> $ <idle>-0       [036] ..s1.   647.428165: kfree_skb: skbaddr=000000004d037db6 protocol=2048 location=0000000074cd1243 reason: NO_SOCKET
> $ <idle>-0       [020] ..s2.   639.676674: kfree_skb: skbaddr=00000000bcbfa42d protocol=2048 location=00000000bfe89d35 reason: PROTO_MEM
> 
> From the reason 'PROTO_MEM' we can know that the skb is dropped because
> the memory configured in net.ipv4.tcp_mem is up to the limition.
> 
> Changes since v1:
> - enrich the document for this series patches in the cover letter,
>   as Eric suggested
> - fix compile warning report by Jakub in the 6th patch
> - let NO_SOCKET trump the XFRM failure in the 2th and 3th patches
> 
> Menglong Dong (9):
>   net: tcp: introduce tcp_drop_reason()
>   net: tcp: add skb drop reasons to tcp_v4_rcv()
>   net: tcp: use kfree_skb_reason() for tcp_v6_rcv()
>   net: tcp: add skb drop reasons to tcp_v{4,6}_inbound_md5_hash()
>   net: tcp: add skb drop reasons to tcp_add_backlog()
>   net: tcp: use kfree_skb_reason() for tcp_v{4,6}_do_rcv()
>   net: tcp: use tcp_drop_reason() for tcp_rcv_established()
>   net: tcp: use tcp_drop_reason() for tcp_data_queue()
>   net: tcp: use tcp_drop_reason() for tcp_data_queue_ofo()
> 
>  include/linux/skbuff.h     | 34 ++++++++++++++++++++++++++++++
>  include/net/tcp.h          |  3 ++-
>  include/trace/events/skb.h | 10 +++++++++
>  net/ipv4/tcp_input.c       | 42 +++++++++++++++++++++++++++++---------
>  net/ipv4/tcp_ipv4.c        | 32 +++++++++++++++++++++--------
>  net/ipv6/tcp_ipv6.c        | 39 +++++++++++++++++++++++++++--------
>  6 files changed, 132 insertions(+), 28 deletions(-)
> 

LGTM. for the set:

Reviewed-by: David Ahern <dsahern@kernel.org>


      parent reply	other threads:[~2022-02-18 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  8:31 [PATCH net-next v2 0/9] net: add skb drop reasons to TCP packet receive menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 1/9] net: tcp: introduce tcp_drop_reason() menglong8.dong
2022-02-19  4:40   ` Jakub Kicinski
2022-02-18  8:31 ` [PATCH net-next v2 2/9] net: tcp: add skb drop reasons to tcp_v4_rcv() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 3/9] net: tcp: use kfree_skb_reason() for tcp_v6_rcv() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 4/9] net: tcp: add skb drop reasons to tcp_v{4,6}_inbound_md5_hash() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 5/9] net: tcp: add skb drop reasons to tcp_add_backlog() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 6/9] net: tcp: use kfree_skb_reason() for tcp_v{4,6}_do_rcv() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 7/9] net: tcp: use tcp_drop_reason() for tcp_rcv_established() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 8/9] net: tcp: use tcp_drop_reason() for tcp_data_queue() menglong8.dong
2022-02-18  8:31 ` [PATCH net-next v2 9/9] net: tcp: use tcp_drop_reason() for tcp_data_queue_ofo() menglong8.dong
2022-02-18 18:51 ` [PATCH net-next v2 0/9] net: add skb drop reasons to TCP packet receive Eric Dumazet
2022-02-18 21:23 ` David Ahern [this message]

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=ac145b7b-8c78-88dd-ded5-c780bf7e94e1@kernel.org \
    --to=dsahern@kernel.org \
    --cc=alobakin@pm.me \
    --cc=arnd@arndb.de \
    --cc=ast@kernel.org \
    --cc=atenart@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=flyingpeng@tencent.com \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=imagedong@tencent.com \
    --cc=john.fastabend@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=memxor@gmail.com \
    --cc=menglong8.dong@gmail.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roopa@nvidia.com \
    --cc=rostedt@goodmis.org \
    --cc=talalahmad@google.com \
    --cc=vvs@virtuozzo.com \
    --cc=willemb@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