From: patchwork-bot+netdevbpf@kernel.org
To: Chenguang Zhao <chenguang.zhao@linux.dev>
Cc: bh74.an@samsung.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, zhaochenguang@kylinos.cn
Subject: Re: [PATCH net v3 0/2] net: sxgbe: fix descriptor ring allocation failure handling
Date: Wed, 29 Jul 2026 08:40:07 +0000 [thread overview]
Message-ID: <178531440719.2521418.13788561990285994467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723021820.203960-1-chenguang.zhao@linux.dev>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 23 Jul 2026 10:18:18 +0800 you wrote:
> From: Chenguang Zhao <zhaochenguang@kylinos.cn>
>
> init_dma_desc_rings() leaks already-allocated TX rings
> when RX allocation fails, and sxgbe_open() ignores its
> return value and continues with invalid DMA rings. Fix
> the cleanup path and check the error.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: sxgbe: free TX rings on RX allocation failure
https://git.kernel.org/netdev/net/c/c870f7e2890b
- [net,v3,2/2] net: sxgbe: check descriptor ring allocation failures
https://git.kernel.org/netdev/net/c/51b093a7ba27
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-07-29 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 2:18 [PATCH net v3 0/2] net: sxgbe: fix descriptor ring allocation failure handling Chenguang Zhao
2026-07-23 2:18 ` [PATCH net v3 1/2] net: sxgbe: free TX rings on RX allocation failure Chenguang Zhao
2026-07-23 10:07 ` Vadim Fedorenko
2026-07-23 2:18 ` [PATCH net v3 2/2] net: sxgbe: check descriptor ring allocation failures Chenguang Zhao
2026-07-23 10:11 ` Vadim Fedorenko
2026-07-23 13:42 ` [PATCH net v3 0/2] net: sxgbe: fix descriptor ring allocation failure handling Jakub Kicinski
2026-07-29 8: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=178531440719.2521418.13788561990285994467.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bh74.an@samsung.com \
--cc=chenguang.zhao@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zhaochenguang@kylinos.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 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.