From: Yuan Can <yuancan@huawei.com>
To: <jesse.brandeburg@intel.com>, <anthony.l.nguyen@intel.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <alice.michael@intel.com>,
<piotr.marczak@intel.com>, <jeffrey.t.kirsher@intel.com>,
<leon@kernel.org>, <jiri@resnulli.us>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Cc: yuancan@huawei.com
Subject: [Intel-wired-lan] [PATCH net v3] intel/i40e: Fix potential memory leak in i40e_init_recovery_mode()
Date: Tue, 6 Dec 2022 13:41:46 +0000 [thread overview]
Message-ID: <20221206134146.36465-1-yuancan@huawei.com> (raw)
The error handling path of i40e_init_recovery_mode() does not handle the
vsi->netdev and pf->vsi, and resource leak can happen if error occurs.
In the meantime, the i40e_probe() returns directly without release
pf->qp_pile when i40e_init_recovery_mode() failed.
Fix by properly releasing vsi->netdev in the error handling path of
i40e_init_recovery_mode() and relying on the error handling path of
i40e_probe() to release pf->vsi and pf->qp_pile if anything goes wrong.
Fixes: 4ff0ee1af016 ("i40e: Introduce recovery mode support")
Signed-off-by: Yuan Can <yuancan@huawei.com>
---
Changes in v3:
- Introduce more error handling path to handle vsi->netdev
- Rely on error path of i40e_probe() instead of do all cleanup in
i40e_init_recovery_mode() to make sure pf->qp_pile is not leaked
Changes in v2:
- Add net in patch title
- Add Leon Romanovsky's reviewed by
drivers/net/ethernet/intel/i40e/i40e_main.c | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
index b5dcd15ced36..d1aadd298ea7 100644
--- a/drivers/net/ethernet/intel/i40e/i40e_main.c
+++ b/drivers/net/ethernet/intel/i40e/i40e_main.c
@@ -15511,13 +15511,13 @@ static int i40e_init_recovery_mode(struct i40e_pf *pf, struct i40e_hw *hw)
goto err_switch_setup;
err = register_netdev(vsi->netdev);
if (err)
- goto err_switch_setup;
+ goto free_netdev;
vsi->netdev_registered = true;
i40e_dbg_pf_init(pf);
err = i40e_setup_misc_vector_for_recovery_mode(pf);
if (err)
- goto err_switch_setup;
+ goto unreg_netdev;
/* tell the firmware that we're starting */
i40e_send_version(pf);
@@ -15528,15 +15528,15 @@ static int i40e_init_recovery_mode(struct i40e_pf *pf, struct i40e_hw *hw)
return 0;
+unreg_netdev:
+ unregister_netdev(vsi->netdev);
+free_netdev:
+ free_netdev(vsi->netdev);
err_switch_setup:
i40e_reset_interrupt_capability(pf);
del_timer_sync(&pf->service_timer);
i40e_shutdown_adminq(hw);
- iounmap(hw->hw_addr);
- pci_disable_pcie_error_reporting(pf->pdev);
- pci_release_mem_regions(pf->pdev);
- pci_disable_device(pf->pdev);
- kfree(pf);
+ kfree(pf->vsi);
return err;
}
@@ -15789,8 +15789,11 @@ static int i40e_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
goto err_sw_init;
}
- if (test_bit(__I40E_RECOVERY_MODE, pf->state))
- return i40e_init_recovery_mode(pf, hw);
+ if (test_bit(__I40E_RECOVERY_MODE, pf->state)) {
+ err = i40e_init_recovery_mode(pf, hw);
+ if (err)
+ goto err_init_lan_hmc;
+ }
err = i40e_init_lan_hmc(hw, hw->func_caps.num_tx_qp,
hw->func_caps.num_rx_qp, 0, 0);
--
2.17.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-12-06 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 13:41 Yuan Can [this message]
2022-12-06 16:54 ` [Intel-wired-lan] [PATCH net v3] intel/i40e: Fix potential memory leak in i40e_init_recovery_mode() Jiri Pirko
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=20221206134146.36465-1-yuancan@huawei.com \
--to=yuancan@huawei.com \
--cc=alice.michael@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotr.marczak@intel.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