From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Anurag Mandal <anurag.mandal@intel.com>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH] net/ice: fix PHY capabilities buffer leak
Date: Tue, 6 Oct 2026 11:57:33 +0200 [thread overview]
Message-ID: <ea668450-0d0f-4a7c-b591-3d5e76bf2d34@intel.com> (raw)
In-Reply-To: <20260930165230.342989-1-anurag.mandal@intel.com>
On 9/30/2026 6:52 PM, Anurag Mandal wrote:
> ice_phy_conf_link() allocates the PHY capabilities buffer and only
> then validates hw->port_info.
> If hw->port_info is NULL,it returns directly without freeing
> PHY capabilities buffer causing the buffer leak.
>
> This patch fixes the issue by moving the hw->port_info NULL check
> above the PHY capabilities buffer allocation.
>
> Fixes: 36afbc269081 ("net/ice: support link speed change")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anurag Mandal <anurag.mandal@intel.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2026-10-06 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 16:52 [PATCH] net/ice: fix PHY capabilities buffer leak Anurag Mandal
2026-10-06 9:57 ` Burakov, Anatoly [this message]
2026-10-06 14:00 ` Bruce Richardson
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=ea668450-0d0f-4a7c-b591-3d5e76bf2d34@intel.com \
--to=anatoly.burakov@intel.com \
--cc=anurag.mandal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox