mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: rostedt@goodmis.org, dsahern@kernel.org, mingo@redhat.com,
	davem@davemloft.net, kuba@kernel.org, nhorman@tuxdriver.com,
	edumazet@google.com, yoshfuji@linux-ipv6.org, alobakin@pm.me,
	willemb@google.com, cong.wang@bytedance.com,
	keescook@chromium.org, pabeni@redhat.com, talalahmad@google.com,
	haokexin@gmail.com, ilias.apalodimas@linaro.org,
	memxor@gmail.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,
	jonathan.lemon@gmail.com, imagedong@tencent.com
Subject: Re: [PATCH v4 net-next 0/3] net: skb: introduce kfree_skb_with_reason()
Date: Mon, 10 Jan 2022 00:50:10 +0000	[thread overview]
Message-ID: <164177581045.14212.13471905867793638959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220109063628.526990-1-imagedong@tencent.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  9 Jan 2022 14:36:25 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.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.
> 
> [...]

Here is the summary with links:
  - [v4,net-next,1/3] net: skb: introduce kfree_skb_reason()
    https://git.kernel.org/netdev/net-next/c/c504e5c2f964
  - [v4,net-next,2/3] net: skb: use kfree_skb_reason() in tcp_v4_rcv()
    https://git.kernel.org/netdev/net-next/c/85125597419a
  - [v4,net-next,3/3] net: skb: use kfree_skb_reason() in __udp4_lib_rcv()
    https://git.kernel.org/netdev/net-next/c/1c7fab70df08

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-01-10  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09  6:36 menglong8.dong
2022-01-09  6:36 ` [PATCH v4 net-next 1/3] net: skb: introduce kfree_skb_reason() menglong8.dong
2022-01-09  6:36 ` [PATCH v4 net-next 2/3] net: skb: use kfree_skb_reason() in tcp_v4_rcv() menglong8.dong
2022-01-09  6:36 ` [PATCH v4 net-next 3/3] net: skb: use kfree_skb_reason() in __udp4_lib_rcv() menglong8.dong
2022-01-10  0: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=164177581045.14212.13471905867793638959.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=ilias.apalodimas@linaro.org \
    --cc=imagedong@tencent.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=memxor@gmail.com \
    --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=willemb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®