From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, qitao.xu@bytedance.com, cong.wang@bytedance.com
Subject: Re: [Patch net-next resend v2] net: use %px to print skb address in trace_netif_receive_skb
Date: Thu, 15 Jul 2021 17:40:04 +0000 [thread overview]
Message-ID: <162637080489.16853.12396223625931902483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210715055923.43126-1-xiyou.wangcong@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 14 Jul 2021 22:59:23 -0700 you wrote:
> From: Qitao Xu <qitao.xu@bytedance.com>
>
> The print format of skb adress in tracepoint class net_dev_template
> is changed to %px from %p, because we want to use skb address
> as a quick way to identify a packet.
>
> Note, trace ring buffer is only accessible to privileged users,
> it is safe to use a real kernel address here.
>
> [...]
Here is the summary with links:
- [net-next,resend,v2] net: use %px to print skb address in trace_netif_receive_skb
https://git.kernel.org/netdev/net/c/65875073eddd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-07-15 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 5:59 [Patch net-next resend v2] net: use %px to print skb address in trace_netif_receive_skb Cong Wang
2021-07-15 17:40 ` patchwork-bot+netdevbpf [this message]
2021-07-23 7:09 ` Kees Cook
2021-07-28 3:17 ` Cong Wang
2021-07-28 15:13 ` tracepoints and %p [was: Re: [Patch net-next resend v2] net: use %px to print skb address in trace_netif_receive_skb] Jann Horn
2021-07-28 15:56 ` Steven Rostedt
2021-07-28 18:48 ` Kees Cook
2021-07-28 18:56 ` Jann Horn
2021-07-28 20:41 ` Steven Rostedt
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=162637080489.16853.12396223625931902483.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=netdev@vger.kernel.org \
--cc=qitao.xu@bytedance.com \
--cc=xiyou.wangcong@gmail.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.