From: "Creeley, Brett" <brett.creeley@intel.com>
To: "yongxin.liu@windriver.com" <yongxin.liu@windriver.com>,
"jeffrey.t.kirsher@intel.com" <jeffrey.t.kirsher@intel.com>,
"Chittim, Madhu" <madhu.chittim@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"andrewx.bowers@intel.com" <andrewx.bowers@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] ice: fix memory leak of aRFS after resuming from suspend
Date: Thu, 18 Mar 2021 22:20:25 +0000 [thread overview]
Message-ID: <5c5c7e89492526a7faffec9b03306ceefab86a3c.camel@intel.com> (raw)
In-Reply-To: <20210318081507.36287-1-yongxin.liu@windriver.com>
On Thu, 2021-03-18 at 16:15 +0800, Yongxin Liu wrote:
> In ice_suspend(), ice_clear_interrupt_scheme() is called, and then
> irq_free_descs() will be eventually called to free irq and its
> descriptor.
>
> In ice_resume(), ice_init_interrupt_scheme() is called to allocate
> new irqs.
> However, in ice_rebuild_arfs(), struct irq_glue and struct cpu_rmap
> maybe
> cannot be freed, if the irqs that released in ice_suspend() were
> reassigned
> to other devices, which makes irq descriptor's affinity_notify lost.
>
> So move ice_remove_arfs() before ice_clear_interrupt_scheme(), which
> can
> make sure all irq_glue and cpu_rmap can be correctly released before
> corresponding irq and descriptor are released.
>
> Fix the following memeory leak.
s/memeory/memory
<snip>
> diff --git a/drivers/net/ethernet/intel/ice/ice_arfs.c
> b/drivers/net/ethernet/intel/ice/ice_arfs.c
> index 6560acd76c94..c748d0a5c7d4 100644
> --- a/drivers/net/ethernet/intel/ice/ice_arfs.c
> +++ b/drivers/net/ethernet/intel/ice/ice_arfs.c
> @@ -654,7 +654,6 @@ void ice_rebuild_arfs(struct ice_pf *pf)
> if (!pf_vsi)
> return;
>
> - ice_remove_arfs(pf);
This should not be removed. Removing this would break the
reset flows outside of the suspend/remove case.
> if (ice_set_cpu_rx_rmap(pf_vsi)) {
> dev_err(ice_pf_to_dev(pf), "Failed to rebuild aRFS\n");
> return;
> diff --git a/drivers/net/ethernet/intel/ice/ice_main.c
> b/drivers/net/ethernet/intel/ice/ice_main.c
> index 2c23c8f468a5..dba901bf2b9b 100644
> --- a/drivers/net/ethernet/intel/ice/ice_main.c
> +++ b/drivers/net/ethernet/intel/ice/ice_main.c
> @@ -4568,6 +4568,9 @@ static int __maybe_unused ice_suspend(struct
> device *dev)
> continue;
> ice_vsi_free_q_vectors(pf->vsi[v]);
> }
> + if (test_bit(ICE_FLAG_FD_ENA, pf->flags)) {
> + ice_remove_arfs(pf);
> + }
Braces aren't needed around a single if statement like this.
Also, I don't think this is the right solution. I think a better
approach would be to call ice_free_rx_cpu_map() here. With this,
it seems like no other changes are necessary. It also isn't
necessary to check the ICE_FLAG_FD_ENA bit with this change.
> ice_clear_interrupt_scheme(pf);
>
> pci_save_state(pdev);
next prev parent reply other threads:[~2021-03-18 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 8:15 [PATCH net] ice: fix memory leak of aRFS after resuming from suspend Yongxin Liu
2021-03-18 22:20 ` Creeley, Brett [this message]
2021-03-19 2:33 ` Liu, Yongxin
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=5c5c7e89492526a7faffec9b03306ceefab86a3c.camel@intel.com \
--to=brett.creeley@intel.com \
--cc=andrewx.bowers@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yongxin.liu@windriver.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;
as well as URLs for NNTP newsgroup(s).