From: Paolo Abeni <pabeni@redhat.com>
To: Dexuan Cui <decui@microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
longli@microsoft.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, kotaranov@microsoft.com,
horms@kernel.org, ernis@linux.microsoft.com,
dipayanroy@linux.microsoft.com, kees@kernel.org,
jacob.e.keller@intel.com, ssengar@linux.microsoft.com,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] net: mana: Validate the packet length reported by the NIC
Date: Wed, 8 Jul 2026 12:57:05 +0200 [thread overview]
Message-ID: <d359508d-76a8-4df8-87ef-2767fe7fb40d@redhat.com> (raw)
In-Reply-To: <20260702041237.617719-2-decui@microsoft.com>
On 7/2/26 6:12 AM, Dexuan Cui wrote:
> Validate the packet length reported in the RX CQE before passing it
> to skb processing. The CQE is supplied by the NIC device and should
> not be blindly trusted.
>
> Cc: stable@vger.kernel.org
This need a Fixes: tag, to help stable team backport.
No need to repost: just reply here, and I'll add it while applying the
patch.
Thanks,
Paolo
next prev parent reply other threads:[~2026-07-08 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 4:12 [PATCH net v3 0/2] Fix MANA RX with bounce buffering Dexuan Cui
2026-07-02 4:12 ` [PATCH net v3 1/2] net: mana: Validate the packet length reported by the NIC Dexuan Cui
2026-07-08 10:57 ` Paolo Abeni [this message]
2026-07-08 14:15 ` [EXTERNAL] " Dexuan Cui
2026-07-02 4:12 ` [PATCH net v3 2/2] net: mana: Sync page pool RX frags for CPU Dexuan Cui
2026-07-09 8:40 ` [PATCH net v3 0/2] Fix MANA RX with bounce buffering patchwork-bot+netdevbpf
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=d359508d-76a8-4df8-87ef-2767fe7fb40d@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dipayanroy@linux.microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kees@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=stable@vger.kernel.org \
--cc=wei.liu@kernel.org \
/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.