From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: dsahern@kernel.org, stephen@networkplumber.org,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com, jhs@mojatatu.com
Subject: Re: [PATCH iproute2-next] tc/class: use rtnl_dump_request_n() in tc_class_list()
Date: Thu, 07 May 2026 15:20:04 +0000 [thread overview]
Message-ID: <177816720480.4034455.16026111878922440843.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506160656.1226077-1-edumazet@google.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 6 May 2026 16:06:56 +0000 you wrote:
> strace tc -s class sh dev eth1 parent 2:
>
> strace is fooled with rtnl_dump_request() way:
>
> sendmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000},
> msg_namelen=12,
> msg_iov=[{iov_base={nlmsg_len=36,
> nlmsg_type=RTM_GETTCLASS,
> nlmsg_flags=NLM_F_REQUEST|NLM_F_DUMP,
> nlmsg_seq=1778082626, nlmsg_pid=0},
> iov_len=16},
> {iov_base={nlmsg_len=0, nlmsg_type=NLMSG_NOOP, nlmsg_flags=0, nlmsg_seq=0, nlmsg_pid=131072},
> iov_len=20}],
> msg_iovlen=2, msg_controllen=0, msg_flags=0}, 0) = 36
>
> [...]
Here is the summary with links:
- [iproute2-next] tc/class: use rtnl_dump_request_n() in tc_class_list()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=eff6e4dad32c
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:[~2026-05-07 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 16:06 [PATCH iproute2-next] tc/class: use rtnl_dump_request_n() in tc_class_list() Eric Dumazet
2026-05-07 10:57 ` Jamal Hadi Salim
2026-05-07 15:20 ` 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=177816720480.4034455.16026111878922440843.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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