From: Simon Horman <horms@kernel.org>
To: Gui-Dong Han <hanguidong02@outlook.com>
Cc: przemyslaw.kitszel@intel.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, edumazet@google.com,
netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, baijiaju1990@gmail.com,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH] ice: Fix improper handling of refcount in ice_sriov_set_msix_vec_count()
Date: Sat, 10 Aug 2024 10:10:15 +0100 [thread overview]
Message-ID: <20240810091015.GF1951@kernel.org> (raw)
In-Reply-To: <SY8P300MB0460412FE86859FF97DE6342C0BA2@SY8P300MB0460.AUSP300.PROD.OUTLOOK.COM>
On Fri, Aug 09, 2024 at 12:59:11PM +0800, Gui-Dong Han wrote:
> This patch addresses an issue with improper reference count handling in the
> ice_sriov_set_msix_vec_count() function. Specifically, the function calls
> ice_get_vf_by_id(), which increments the reference count of the vf pointer.
> If the subsequent call to ice_get_vf_vsi() fails, the function currently
> returns an error without decrementing the reference count of the vf
> pointer, leading to a reference count leak.
>
> The correct behavior, as implemented in this patch, is to decrement the
> reference count using ice_put_vf(vf) before returning an error when vsi
> is NULL.
>
> This bug was identified by an experimental static analysis tool developed
> by our team. The tool specializes in analyzing reference count operations
> and identifying potential mismanagement of reference counts. In this case,
> the tool flagged the missing decrement operation as a potential issue,
> leading to this patch.
>
> Fixes: 4035c72dc1ba ("ice: reconfig host after changing MSI-X on VF")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gui-Dong Han <hanguidong02@outlook.com>
Thanks Gui-Dong Han,
I agree with your analysis.
However, I wonder if the same resource leak can occur
in the unroll label, if the if clause results in a return.
It is around line 1444 without your patch applied.
vf->first_vector_idx = ice_sriov_get_irqs(pf, vf->num_msix);
if (vf->first_vector_idx < 0)
return -EINVAL;
> ---
> drivers/net/ethernet/intel/ice/ice_sriov.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_sriov.c b/drivers/net/ethernet/intel/ice/ice_sriov.c
> index 55ef33208456..eb5030aba9a5 100644
> --- a/drivers/net/ethernet/intel/ice/ice_sriov.c
> +++ b/drivers/net/ethernet/intel/ice/ice_sriov.c
> @@ -1096,8 +1096,10 @@ int ice_sriov_set_msix_vec_count(struct pci_dev *vf_dev, int msix_vec_count)
> return -ENOENT;
>
> vsi = ice_get_vf_vsi(vf);
> - if (!vsi)
> + if (!vsi) {
> + ice_put_vf(vf);
> return -ENOENT;
> + }
>
> prev_msix = vf->num_msix;
> prev_queues = vf->num_vf_qs;
> --
> 2.25.1
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Gui-Dong Han <hanguidong02@outlook.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] ice: Fix improper handling of refcount in ice_sriov_set_msix_vec_count()
Date: Sat, 10 Aug 2024 10:10:15 +0100 [thread overview]
Message-ID: <20240810091015.GF1951@kernel.org> (raw)
In-Reply-To: <SY8P300MB0460412FE86859FF97DE6342C0BA2@SY8P300MB0460.AUSP300.PROD.OUTLOOK.COM>
On Fri, Aug 09, 2024 at 12:59:11PM +0800, Gui-Dong Han wrote:
> This patch addresses an issue with improper reference count handling in the
> ice_sriov_set_msix_vec_count() function. Specifically, the function calls
> ice_get_vf_by_id(), which increments the reference count of the vf pointer.
> If the subsequent call to ice_get_vf_vsi() fails, the function currently
> returns an error without decrementing the reference count of the vf
> pointer, leading to a reference count leak.
>
> The correct behavior, as implemented in this patch, is to decrement the
> reference count using ice_put_vf(vf) before returning an error when vsi
> is NULL.
>
> This bug was identified by an experimental static analysis tool developed
> by our team. The tool specializes in analyzing reference count operations
> and identifying potential mismanagement of reference counts. In this case,
> the tool flagged the missing decrement operation as a potential issue,
> leading to this patch.
>
> Fixes: 4035c72dc1ba ("ice: reconfig host after changing MSI-X on VF")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gui-Dong Han <hanguidong02@outlook.com>
Thanks Gui-Dong Han,
I agree with your analysis.
However, I wonder if the same resource leak can occur
in the unroll label, if the if clause results in a return.
It is around line 1444 without your patch applied.
vf->first_vector_idx = ice_sriov_get_irqs(pf, vf->num_msix);
if (vf->first_vector_idx < 0)
return -EINVAL;
> ---
> drivers/net/ethernet/intel/ice/ice_sriov.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_sriov.c b/drivers/net/ethernet/intel/ice/ice_sriov.c
> index 55ef33208456..eb5030aba9a5 100644
> --- a/drivers/net/ethernet/intel/ice/ice_sriov.c
> +++ b/drivers/net/ethernet/intel/ice/ice_sriov.c
> @@ -1096,8 +1096,10 @@ int ice_sriov_set_msix_vec_count(struct pci_dev *vf_dev, int msix_vec_count)
> return -ENOENT;
>
> vsi = ice_get_vf_vsi(vf);
> - if (!vsi)
> + if (!vsi) {
> + ice_put_vf(vf);
> return -ENOENT;
> + }
>
> prev_msix = vf->num_msix;
> prev_queues = vf->num_vf_qs;
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2024-08-10 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 4:59 [Intel-wired-lan] [PATCH] ice: Fix improper handling of refcount in ice_sriov_set_msix_vec_count() Gui-Dong Han
2024-08-09 4:59 ` Gui-Dong Han
2024-08-10 9:10 ` Simon Horman [this message]
2024-08-10 9:10 ` Simon Horman
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=20240810091015.GF1951@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=baijiaju1990@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanguidong02@outlook.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.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.