All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Subject: Re: [PATCH net 1/2] genetlink: report the real command id for dump-only ops in policy dumps
Date: Tue, 22 Sep 2026 13:30:05 +0000	[thread overview]
Message-ID: <179008380590.4078083.13191066424131386086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918222949.4190284-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 18 Sep 2026 15:29:48 -0700 you wrote:
> The op-to-policy map a CTRL_CMD_GETPOLICY dump returns is the only way
> for userspace to find out which policy index belongs to which command.
> ctrl_dumppolicy_put_op() tags the nest with doit->cmd, but an op which
> only has a dumpit has no doit and every path which fills the split ops
> in zeroes it out, so those entries all claim to be command 0.  nlctrl's
> own CTRL_CMD_GETPOLICY and NETDEV_CMD_QSTATS_GET are both in that group:
> 
> [...]

Here is the summary with links:
  - [net,1/2] genetlink: report the real command id for dump-only ops in policy dumps
    https://git.kernel.org/netdev/net/c/261e8a37ecba
  - [net,2/2] selftests: net: nl_nlctrl: check the op ids in the policy map
    https://git.kernel.org/netdev/net/c/a87529034b9c

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



      parent reply	other threads:[~2026-09-22 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 22:29 [PATCH net 1/2] genetlink: report the real command id for dump-only ops in policy dumps Jakub Kicinski
2026-09-18 22:29 ` [PATCH net 2/2] selftests: net: nl_nlctrl: check the op ids in the policy map Jakub Kicinski
2026-09-22 13:30 ` 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=179008380590.4078083.13191066424131386086.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.