From: patchwork-bot+netdevbpf@kernel.org
To: Yan Zhai <yan@cloudflare.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
dsahern@kernel.org, quic_abchauha@quicinc.com,
almasrymina@google.com, fw@strlen.de,
aleksander.lobakin@intel.com, dhowells@redhat.com,
jiri@resnulli.us, daniel@iogearbox.net, bigeasy@linutronix.de,
lorenzo@kernel.org, asml.silence@gmail.com,
linux-kernel@vger.kernel.org, kernel-team@cloudflare.com,
hawk@kernel.org, rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, nhorman@tuxdriver.com,
linux-trace-kernel@vger.kernel.org, dan.carpenter@linaro.org
Subject: Re: [PATCH net-next v5 0/7] net: pass receive socket to drop tracepoint
Date: Wed, 19 Jun 2024 11:50:31 +0000 [thread overview]
Message-ID: <171879783123.2748.515065113481168194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718642328.git.yan@cloudflare.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 17 Jun 2024 11:09:00 -0700 you wrote:
> We set up our production packet drop monitoring around the kfree_skb
> tracepoint. While this tracepoint is extremely valuable for diagnosing
> critical problems, it also has some limitation with drops on the local
> receive path: this tracepoint can only inspect the dropped skb itself,
> but such skb might not carry enough information to:
>
> 1. determine in which netns/container this skb gets dropped
> 2. determine by which socket/service this skb oughts to be received
>
> [...]
Here is the summary with links:
- [net-next,v5,1/7] net: add rx_sk to trace_kfree_skb
https://git.kernel.org/netdev/net-next/c/c53795d48ee8
- [net-next,v5,2/7] net: introduce sk_skb_reason_drop function
https://git.kernel.org/netdev/net-next/c/ba8de796baf4
- [net-next,v5,3/7] ping: use sk_skb_reason_drop to free rx packets
https://git.kernel.org/netdev/net-next/c/7467de17635f
- [net-next,v5,4/7] net: raw: use sk_skb_reason_drop to free rx packets
https://git.kernel.org/netdev/net-next/c/ce9a2424e9da
- [net-next,v5,5/7] tcp: use sk_skb_reason_drop to free rx packets
https://git.kernel.org/netdev/net-next/c/46a02aa35752
- [net-next,v5,6/7] udp: use sk_skb_reason_drop to free rx packets
https://git.kernel.org/netdev/net-next/c/fc0cc9248843
- [net-next,v5,7/7] af_packet: use sk_skb_reason_drop to free rx packets
https://git.kernel.org/netdev/net-next/c/e2e7d78d9a25
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-19 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 18:09 [PATCH net-next v5 0/7] net: pass receive socket to drop tracepoint Yan Zhai
2024-06-17 18:09 ` [PATCH net-next v5 1/7] net: add rx_sk to trace_kfree_skb Yan Zhai
2024-06-18 6:15 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 2/7] net: introduce sk_skb_reason_drop function Yan Zhai
2024-06-18 6:18 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 3/7] ping: use sk_skb_reason_drop to free rx packets Yan Zhai
2024-06-18 6:18 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 4/7] net: raw: " Yan Zhai
2024-06-18 6:19 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 5/7] tcp: " Yan Zhai
2024-06-18 6:21 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 6/7] udp: " Yan Zhai
2024-06-18 6:22 ` Jesper Dangaard Brouer
2024-06-17 18:09 ` [PATCH net-next v5 7/7] af_packet: " Yan Zhai
2024-06-18 6:24 ` Jesper Dangaard Brouer
2024-06-19 11:50 ` 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=171879783123.2748.515065113481168194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=quic_abchauha@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=yan@cloudflare.com \
/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.