From: patchwork-bot+netdevbpf@kernel.org
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: almasrymina@google.com, bcf@google.com, joshwash@google.com,
willemb@google.com, pkaligineedi@google.com, pabeni@redhat.com,
kuba@kernel.org, jeroendb@google.com, hramamurthy@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
darren.kenny@oracle.com
Subject: Re: [PATCH net v2] gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO
Date: Wed, 04 Jun 2025 11:40:28 +0000 [thread overview]
Message-ID: <174903722800.2252645.3715137704739506343.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250602103450.3472509-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 2 Jun 2025 03:34:29 -0700 you wrote:
> gve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()
> did not check for this case before dereferencing the returned pointer.
>
> Add a missing NULL check to prevent a potential NULL pointer
> dereference when allocation fails.
>
> This improves robustness in low-memory scenarios.
>
> [...]
Here is the summary with links:
- [net,v2] gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO
https://git.kernel.org/netdev/net/c/12c331b29c73
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-06-04 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 10:34 [PATCH net v2] gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO Alok Tiwari
2025-06-03 8:25 ` Simon Horman
2025-06-04 11: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=174903722800.2252645.3715137704739506343.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcf@google.com \
--cc=darren.kenny@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=willemb@google.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 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).