From: Jacob Keller <jacob.e.keller@intel.com>
To: Marcin Szycik <marcin.szycik@linux.intel.com>,
Dawei Feng <dawei.feng@seu.edu.cn>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jianhao.xu@seu.edu.cn>,
<stable@vger.kernel.org>, Zilin Guan <zilin@seu.edu.cn>
Subject: Re: [Intel-wired-lan] [PATCH net] ice: fix memory leak in ice_lbtest_prepare_rings()
Date: Tue, 9 Jun 2026 15:27:51 -0700 [thread overview]
Message-ID: <00f5f6e3-e80f-4c16-8d2f-f8148bcddfa8@intel.com> (raw)
In-Reply-To: <ea66e44e-c9b0-4942-af6f-0b76e3f065a1@linux.intel.com>
On 6/9/2026 7:27 AM, Marcin Szycik wrote:
>
>
> On 09.06.2026 14:50, Dawei Feng wrote:
>> While ice_lbtest_prepare_rings() correctly frees Rx rings if
>> ice_vsi_start_all_rx_rings() fails, the earlier error paths for
>> ice_vsi_setup_rx_rings() and ice_vsi_cfg_lan() jump past this cleanup.
>> If Rx ring setup or LAN configuration fails, the function leaks the
>> initialized Rx resources.
>>
>> Fix this by routing these earlier failures to the existing
>> err_start_rx_ring label. This ensures the Rx rings are properly freed
>> before tearing down the Tx state.
>>
>> The bug was first flagged by an experimental analysis tool we are
>> developing for kernel memory-management bugs while analyzing
>> v6.13-rc1. The tool is still under development and is not yet publicly
>> available. Manual inspection confirms that the bug is still
>> present in v7.1-rc5.
>>
>> An x86_64 allyesconfig build showed no new warnings. As we do not have an
>> Intel E800 Series adapter available to run the ethtool offline loopback
>> selftest, no runtime testing was able to be performed.
>
> IMO last two paragraphs should not be included in commit message,
> rather after ---.
>
If this gets queued up by Tony it will get testing by Intel's validation
team ya.
>> Fixes: 0e674aeb0b77 ("ice: Add handler for ethtool selftest")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Zilin Guan <zilin@seu.edu.cn>
>> Signed-off-by: Dawei Feng <dawei.feng@seu.edu.cn>
>> ---
>> drivers/net/ethernet/intel/ice/ice_ethtool.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_ethtool.c b/drivers/net/ethernet/intel/ice/ice_ethtool.c
>> index f28416a707d7..7c81ca313645 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_ethtool.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_ethtool.c
>> @@ -1065,11 +1065,11 @@ static int ice_lbtest_prepare_rings(struct ice_vsi *vsi)
>>
>> status = ice_vsi_setup_rx_rings(vsi);
>> if (status)
>> - goto err_setup_rx_ring;
>> + goto err_start_rx_ring;
>>
>> status = ice_vsi_cfg_lan(vsi);
>> if (status)
>> - goto err_setup_rx_ring;
>> + goto err_start_rx_ring;
>>
>> status = ice_vsi_start_all_rx_rings(vsi);
>> if (status)
>> @@ -1079,7 +1079,6 @@ static int ice_lbtest_prepare_rings(struct ice_vsi *vsi)
>>
>> err_start_rx_ring:
>> ice_vsi_free_rx_rings(vsi);
>> -err_setup_rx_ring:
>> ice_vsi_stop_lan_tx_rings(vsi, ICE_NO_RESET, 0);
>
> Correct me if I'm wrong, but looks like unroll order is reversed:
> ice_vsi_stop_lan_tx_rings() unrolls ice_vsi_cfg_lan()
> ice_vsi_free_rx_rings() unrolls ice_vsi_setup_rx_rings()
> (was reversed before this patch too, but since we're fixing it, might as well)
>
>> err_setup_tx_ring:
>> ice_vsi_free_tx_rings(vsi);
>
> Thanks,
> Marcin
next prev parent reply other threads:[~2026-06-09 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:50 [PATCH net] ice: fix memory leak in ice_lbtest_prepare_rings() Dawei Feng
2026-06-09 14:27 ` [Intel-wired-lan] " Marcin Szycik
2026-06-09 22:27 ` Jacob Keller [this message]
2026-06-11 2:02 ` Dawei Feng
2026-06-11 9:57 ` Marcin Szycik
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=00f5f6e3-e80f-4c16-8d2f-f8148bcddfa8@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dawei.feng@seu.edu.cn \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.kernel.org \
--cc=zilin@seu.edu.cn \
/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