BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: dsahern@kernel.org, kuba@kernel.org, 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,
	mengensun@tencent.com
Subject: Re: [PATCH net-next v3 0/9] net: add skb drop reasons to TCP packet receive
Date: Sun, 20 Feb 2022 14:30:11 +0000	[thread overview]
Message-ID: <164536741158.13103.3993205016299229625.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220220070637.162720-1-imagedong@tencent.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Sun, 20 Feb 2022 15:06:28 +0800 you 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:
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/9] net: tcp: introduce tcp_drop_reason()
    https://git.kernel.org/netdev/net-next/c/082116ffcb74
  - [net-next,v3,2/9] net: tcp: add skb drop reasons to tcp_v4_rcv()
    https://git.kernel.org/netdev/net-next/c/255f9034d305
  - [net-next,v3,3/9] net: tcp: use kfree_skb_reason() for tcp_v6_rcv()
    https://git.kernel.org/netdev/net-next/c/c0e3154d9c88
  - [net-next,v3,4/9] net: tcp: add skb drop reasons to tcp_v{4,6}_inbound_md5_hash()
    https://git.kernel.org/netdev/net-next/c/643b622b51f1
  - [net-next,v3,5/9] net: tcp: add skb drop reasons to tcp_add_backlog()
    https://git.kernel.org/netdev/net-next/c/7a26dc9e7b43
  - [net-next,v3,6/9] net: tcp: use kfree_skb_reason() for tcp_v{4,6}_do_rcv()
    https://git.kernel.org/netdev/net-next/c/8eba65fa5f06
  - [net-next,v3,7/9] net: tcp: use tcp_drop_reason() for tcp_rcv_established()
    https://git.kernel.org/netdev/net-next/c/2a968ef60e1f
  - [net-next,v3,8/9] net: tcp: use tcp_drop_reason() for tcp_data_queue()
    https://git.kernel.org/netdev/net-next/c/a7ec381049c0
  - [net-next,v3,9/9] net: tcp: use tcp_drop_reason() for tcp_data_queue_ofo()
    https://git.kernel.org/netdev/net-next/c/d25e481be0c5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-02-20 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20  7:06 [PATCH net-next v3 0/9] net: add skb drop reasons to TCP packet receive menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 1/9] net: tcp: introduce tcp_drop_reason() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 2/9] net: tcp: add skb drop reasons to tcp_v4_rcv() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 3/9] net: tcp: use kfree_skb_reason() for tcp_v6_rcv() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 4/9] net: tcp: add skb drop reasons to tcp_v{4,6}_inbound_md5_hash() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 5/9] net: tcp: add skb drop reasons to tcp_add_backlog() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 6/9] net: tcp: use kfree_skb_reason() for tcp_v{4,6}_do_rcv() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 7/9] net: tcp: use tcp_drop_reason() for tcp_rcv_established() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 8/9] net: tcp: use tcp_drop_reason() for tcp_data_queue() menglong8.dong
2022-02-20  7:06 ` [PATCH net-next v3 9/9] net: tcp: use tcp_drop_reason() for tcp_data_queue_ofo() menglong8.dong
2022-02-20 14:30 ` patchwork-bot+netdevbpf [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=164536741158.13103.3993205016299229625.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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=dsahern@kernel.org \
    --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=mengensun@tencent.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