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: edumazet@google.com, kuba@kernel.org, davem@davemloft.net,
	pabeni@redhat.com, rostedt@goodmis.org, mingo@redhat.com,
	imagedong@tencent.com, dsahern@kernel.org,
	flyingpeng@tencent.com, dongli.zhang@oracle.com, robh@kernel.org,
	asml.silence@gmail.com, luiz.von.dentz@intel.com,
	vasily.averin@linux.dev, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net v3] net: skb: export skb drop reaons to user by TRACE_DEFINE_ENUM
Date: Wed, 07 Sep 2022 15:00:15 +0000	[thread overview]
Message-ID: <166256281591.26447.5640318834155971016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220905035015.1130730-1-imagedong@tencent.com>

Hello:

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

On Mon,  5 Sep 2022 11:50:15 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
> 
> As Eric reported, the 'reason' field is not presented when trace the
> kfree_skb event by perf:
> 
> $ perf record -e skb:kfree_skb -a sleep 10
> $ perf script
>   ip_defrag 14605 [021]   221.614303:   skb:kfree_skb:
>   skbaddr=0xffff9d2851242700 protocol=34525 location=0xffffffffa39346b1
>   reason:
> 
> [...]

Here is the summary with links:
  - [net,v3] net: skb: export skb drop reaons to user by TRACE_DEFINE_ENUM
    https://git.kernel.org/netdev/net/c/9cb252c4c1c5

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



      reply	other threads:[~2022-09-07 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  3:50 menglong8.dong
2022-09-07 15:00 ` 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=166256281591.26447.5640318834155971016.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=asml.silence@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dongli.zhang@oracle.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=flyingpeng@tencent.com \
    --cc=imagedong@tencent.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=menglong8.dong@gmail.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vasily.averin@linux.dev \
    /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®