From: patchwork-bot+netdevbpf@kernel.org
To: Md Rabbani <rabbanyhmm@gmail.com>
Cc: maxime.chevallier@bootlin.com, alexandre.torgue@foss.st.com,
mcoquelin.stm32@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] net: stmmac: fix device node reference leaks in stmmac_mtl_setup()
Date: Mon, 24 Aug 2026 18:50:15 +0000 [thread overview]
Message-ID: <178759741588.3062482.17874707106135640490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260821055718.57-1-rabbanyhmm@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 21 Aug 2026 11:57:18 +0600 you wrote:
> In stmmac_mtl_setup(), q_node is shared across the RX and TX queue
> parsing loops. When the RX queue loop breaks early because the number
> of parsed queues reaches plat->rx_queues_to_use, q_node retains an
> acquired reference count. If the error check passes
> (queue == plat->rx_queues_to_use), execution proceeds directly to the
> TX queue loop, where of_get_next_child() immediately overwrites q_node
> with the first TX child, permanently leaking the retained RX child
> device node reference.
>
> [...]
Here is the summary with links:
- net: stmmac: fix device node reference leaks in stmmac_mtl_setup()
https://git.kernel.org/netdev/net/c/317fe168f4c0
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-08-24 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 5:57 [PATCH] net: stmmac: fix device node reference leaks in stmmac_mtl_setup() Md Rabbani
2026-08-24 18:50 ` 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=178759741588.3062482.17874707106135640490.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rabbanyhmm@gmail.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.