From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
idosch@nvidia.com, vulab@iscas.ac.cn, mlxsw@nvidia.com
Subject: Re: [PATCH net 0/2] mlxsw: Fix port range register leak
Date: Thu, 08 Oct 2026 18:00:05 +0000 [thread overview]
Message-ID: <179148240553.372666.3460910775211213373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1791294384.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 6 Oct 2026 16:21:27 +0200 you wrote:
> When the mlxsw driver parses a port range template rule, it acquires the
> actual port range registers. The parsing is only done to determine the
> element usage, so the registers can be deallocated right away, but this is
> never done, and the registers are leaked. Plug this leak and add a selftest
> that would have caught it.
>
> Petr Machata (2):
> mlxsw: spectrum_flower: Fix port range register leak in tmplt_create()
> selftests: mlxsw: Test port range occupancy on template create
>
> [...]
Here is the summary with links:
- [net,1/2] mlxsw: spectrum_flower: Fix port range register leak in tmplt_create()
https://git.kernel.org/netdev/net/c/7ea07afb230f
- [net,2/2] selftests: mlxsw: Test port range occupancy on template create
https://git.kernel.org/netdev/net/c/71198b59df56
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-10-08 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 14:21 [PATCH net 0/2] mlxsw: Fix port range register leak Petr Machata
2026-10-06 14:21 ` [PATCH net 1/2] mlxsw: spectrum_flower: Fix port range register leak in tmplt_create() Petr Machata
2026-10-06 21:49 ` Jacob Keller
2026-10-06 14:21 ` [PATCH net 2/2] selftests: mlxsw: Test port range occupancy on template create Petr Machata
2026-10-06 21:50 ` Jacob Keller
2026-10-08 18: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=179148240553.372666.3460910775211213373.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vulab@iscas.ac.cn \
/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