diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-08 10:49:26 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-08 10:49:26 -0700 |
| commit | ff6f5157e034f81c2d6482259fc656cd0fe5a8ff (patch) | |
| tree | 829db06971b3900b274aa125a0883e57b911effe /tools/lib/python | |
| parent | fc13ba44da197a186f2f4d77c5b7d73d0f99f053 (diff) | |
| parent | 71198b59df56a9a0115115091cc1aad2a4e3c74d (diff) | |
| download | linux-next-ff6f5157e034f81c2d6482259fc656cd0fe5a8ff.tar.gz linux-next-ff6f5157e034f81c2d6482259fc656cd0fe5a8ff.zip | |
Merge branch 'mlxsw-fix-port-range-register-leak'
Petr Machata says:
====================
mlxsw: Fix port range register leak
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.
====================
Link: https://patch.msgid.link/cover.1791294384.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions