From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, dsahern@kernel.org,
petrm@nvidia.com
Subject: Re: [PATCH net 0/3] nexthop: Nexthop dump fixes
Date: Wed, 09 Aug 2023 21:00:22 +0000 [thread overview]
Message-ID: <169161482226.5018.9274281579069243398.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230808075233.3337922-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Aug 2023 10:52:30 +0300 you wrote:
> Patches #1 and #3 fix two problems related to nexthops and nexthop
> buckets dump, respectively. Patch #2 is a preparation for the third
> patch.
>
> The pattern described in these patches of splitting the NLMSG_DONE to a
> separate response is prevalent in other rtnetlink dump callbacks. I
> don't know if it's because I'm missing something or if this was done
> intentionally to ensure the message is delivered to user space. After
> commit 0642840b8bb0 ("af_netlink: ensure that NLMSG_DONE never fails in
> dumps") this is no longer necessary and I can improve these dump
> callbacks assuming this analysis is correct.
>
> [...]
Here is the summary with links:
- [net,1/3] nexthop: Fix infinite nexthop dump when using maximum nexthop ID
https://git.kernel.org/netdev/net/c/913f60cacda7
- [net,2/3] nexthop: Make nexthop bucket dump more efficient
https://git.kernel.org/netdev/net/c/f10d3d9df49d
- [net,3/3] nexthop: Fix infinite nexthop bucket dump when using maximum nexthop ID
https://git.kernel.org/netdev/net/c/8743aeff5bc4
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:[~2023-08-09 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:52 [PATCH net 0/3] nexthop: Nexthop dump fixes Ido Schimmel
2023-08-08 7:52 ` [PATCH net 1/3] nexthop: Fix infinite nexthop dump when using maximum nexthop ID Ido Schimmel
2023-08-08 14:53 ` David Ahern
2023-08-08 7:52 ` [PATCH net 2/3] nexthop: Make nexthop bucket dump more efficient Ido Schimmel
2023-08-08 14:53 ` David Ahern
2023-08-08 7:52 ` [PATCH net 3/3] nexthop: Fix infinite nexthop bucket dump when using maximum nexthop ID Ido Schimmel
2023-08-08 14:54 ` David Ahern
2023-08-09 21: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=169161482226.5018.9274281579069243398.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).