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,
horms@kernel.org, penguin-kernel@I-love.SAKURA.ne.jp
Subject: Re: [PATCH net 1/2] ipv4: Fix reference count leak when using error routes with nexthop objects
Date: Tue, 30 Dec 2025 09:40:08 +0000 [thread overview]
Message-ID: <176708760854.3192123.12598884931818074105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251221144829.197694-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 21 Dec 2025 16:48:28 +0200 you wrote:
> When a nexthop object is deleted, it is marked as dead and then
> fib_table_flush() is called to flush all the routes that are using the
> dead nexthop.
>
> The current logic in fib_table_flush() is to only flush error routes
> (e.g., blackhole) when it is called as part of network namespace
> dismantle (i.e., with flush_all=true). Therefore, error routes are not
> flushed when their nexthop object is deleted:
>
> [...]
Here is the summary with links:
- [net,1/2] ipv4: Fix reference count leak when using error routes with nexthop objects
https://git.kernel.org/netdev/net/c/ac782f4e3bfc
- [net,2/2] selftests: fib_nexthops: Add test cases for error routes deletion
https://git.kernel.org/netdev/net/c/44741e9de29b
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:[~2025-12-30 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 14:48 [PATCH net 1/2] ipv4: Fix reference count leak when using error routes with nexthop objects Ido Schimmel
2025-12-21 14:48 ` [PATCH net 2/2] selftests: fib_nexthops: Add test cases for error routes deletion Ido Schimmel
2025-12-22 23:13 ` David Ahern
2025-12-22 23:12 ` [PATCH net 1/2] ipv4: Fix reference count leak when using error routes with nexthop objects David Ahern
2025-12-30 9:40 ` 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=176708760854.3192123.12598884931818074105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).