From: patchwork-bot+netdevbpf@kernel.org
To: Vaibhav Nagare <nagarevaibhav@gmail.com>
Cc: horms@kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, andrew+netdev@lunn.ch,
matvey.kovalev@ispras.ru, Pavel.Zhigulin@kaspersky.com,
aelior@marvell.com, manishc@marvell.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
vnagare@redhat.com
Subject: Re: [PATCH net v5] qede: Fix NULL pointer dereference in TPA fragment processing
Date: Sat, 22 Aug 2026 20:30:22 +0000 [thread overview]
Message-ID: <178743062214.1819488.4090246622562487688.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260818073309.2266072-1-vnagare@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Aug 2026 13:03:09 +0530 you wrote:
> Under memory pressure, the qede driver encounters NULL pointer
> dereferences when processing TPA continuation fragments.
>
> Commit 8a8633978b84 ("qede: Add build_skb() support.") accidentally
> dropped the assignment of tpa_info->buffer.data in qede_tpa_start().
>
> When memory pressure causes an SKB allocation failure in qede_tpa_start(),
> the driver sets tpa_start_fail = true and attempts to recycle the physical
> page later in qede_tpa_end() via qede_reuse_page(). However, because
> buffer.data was left uninitialized (NULL), qede_reuse_page() pushes a
> "ghost" BD (valid DMA mapping but NULL data pointer) back into the
> active Rx ring.
>
> [...]
Here is the summary with links:
- [net,v5] qede: Fix NULL pointer dereference in TPA fragment processing
https://git.kernel.org/netdev/net/c/06aa3d26327f
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-22 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 7:33 [PATCH net v5] qede: Fix NULL pointer dereference in TPA fragment processing Vaibhav Nagare
2026-08-22 20:30 ` 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=178743062214.1819488.4090246622562487688.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Pavel.Zhigulin@kaspersky.com \
--cc=aelior@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=matvey.kovalev@ispras.ru \
--cc=nagarevaibhav@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vnagare@redhat.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