mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vaibhav Nagare <nagarevaibhav@gmail.com>
Cc: horms@kernel.org, davem@davemloft.net, 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,
	Vaibhav Nagare <vnagare@redhat.com>
Subject: Re: [PATCH net v2] qede: Fix NULL pointer dereference in TPA fragment processing
Date: Mon, 27 Jul 2026 17:03:08 -0700	[thread overview]
Message-ID: <20260727170308.5199f377@kernel.org> (raw)
In-Reply-To: <20260724140044.1055918-1-vnagare@redhat.com>

Please don't post in reply to previous posting, and...

On Fri, 24 Jul 2026 19:30:44 +0530 Vaibhav Nagare wrote:
> Fix by:
> 1. Adding NULL page validation in qede_fill_frag_skb() before dereferencing
> 2. Checking error state EARLY in qede_tpa_end() before processing fragments
> 3. Checking error state in qede_tpa_cont() to skip fragment processing
> 
> This allows the system to survive memory pressure by dropping packets
> instead of crashing.
> 
> Fixes: 55482edc25f0 ("qede: Add slowpath/fastpath support and enable hardware GRO")
> Cc: stable@vger.kernel.org
> 

.. remove this empty line ..

> Signed-off-by: Vaibhav Nagare <vnagare@redhat.com>
> 

.. and the --- separator should be added here, before the change long.

>   v2: Addressed AI review feedback from Simon Horman:
>     - Added net_ratelimit() to prevent printk storm in NAPI fast path
>     - Fixed NULL buffer recycling: check if page is valid before recycling,
>       otherwise just consume the BD to prevent NULL from re-entering the ring
>     - Added proper cleanup in qede_tpa_end() before early exit to prevent
>       memory leaks and ring desynchronization (DMA unmap + BD recycling)
> 
>   v1: https://lore.kernel.org/netdev/20260709044704.141507-1-vnagare@redhat.com/

I sent out the latest AI complaints. 

      parent reply	other threads:[~2026-07-28  0:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  4:47 [PATCH net] " Vaibhav Nagare
2026-07-16  8:47 ` Simon Horman
2026-07-24 14:00   ` [PATCH net v2] " Vaibhav Nagare
2026-07-24 15:16     ` Markus Elfring
2026-07-28  0:01     ` Jakub Kicinski
2026-07-28  0:03     ` Jakub Kicinski [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=20260727170308.5199f377@kernel.org \
    --to=kuba@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=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

all inboxes | Powered by JetHome®