From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Tong Zhang <ztong0001@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Wojciech Ziemba <wojciech.ziemba@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] crypto: qat - dont release uninitialized resources
Date: Thu, 18 Mar 2021 15:53:03 +0000 [thread overview]
Message-ID: <YFN3X6q8dzEaUp27@silpixa00400314> (raw)
In-Reply-To: <20210312162203.2416149-2-ztong0001@gmail.com>
On Fri, Mar 12, 2021 at 11:22:02AM -0500, Tong Zhang wrote:
> adf_vf_isr_resource_alloc() is not unwinding correctly when error
> happens and it trys to release uninitialized resources.
> To fix this, only release initialized resources.
>
> [ 1.792845] Trying to free already-free IRQ 11
> [ 1.793091] WARNING: CPU: 0 PID: 182 at kernel/irq/manage.c:1821 free_irq+0x202/0x380
> [ 1.801340] Call Trace:
> [ 1.801477] adf_vf_isr_resource_free+0x32/0xb0 [intel_qat]
> [ 1.801785] adf_vf_isr_resource_alloc+0x14d/0x150 [intel_qat]
> [ 1.802105] adf_dev_init+0xba/0x140 [intel_qat]
>
> Signed-off-by: Tong Zhang <ztong0001@gmail.com>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
I would add also a Fixes tag:
Fixes: dd0f368398ea ("crypto: qat - Add qat dh895xcc VF driver")
Minor nit, typo in commit message: dont --> don't/do not
Apart from that
Acked-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
--
Giovanni
> ---
> drivers/crypto/qat/qat_common/adf_vf_isr.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/qat/qat_common/adf_vf_isr.c b/drivers/crypto/qat/qat_common/adf_vf_isr.c
> index 38d316a42ba6..888388acb6bd 100644
> --- a/drivers/crypto/qat/qat_common/adf_vf_isr.c
> +++ b/drivers/crypto/qat/qat_common/adf_vf_isr.c
> @@ -261,17 +261,26 @@ int adf_vf_isr_resource_alloc(struct adf_accel_dev *accel_dev)
> goto err_out;
>
> if (adf_setup_pf2vf_bh(accel_dev))
> - goto err_out;
> + goto err_disable_msi;
>
> if (adf_setup_bh(accel_dev))
> - goto err_out;
> + goto err_cleanup_pf2vf_bh;
>
> if (adf_request_msi_irq(accel_dev))
> - goto err_out;
> + goto err_cleanup_bh;
>
> return 0;
> +
> +err_cleanup_bh:
> + adf_cleanup_bh(accel_dev);
> +
> +err_cleanup_pf2vf_bh:
> + adf_cleanup_pf2vf_bh(accel_dev);
> +
> +err_disable_msi:
> + adf_disable_msi(accel_dev);
> +
> err_out:
> - adf_vf_isr_resource_free(accel_dev);
> return -EFAULT;
> }
> EXPORT_SYMBOL_GPL(adf_vf_isr_resource_alloc);
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-03-18 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:22 [PATCH v3 0/2] crypto: qat: fix couple crashes duing error handling Tong Zhang
2021-03-12 16:22 ` [PATCH v3 1/2] crypto: qat - dont release uninitialized resources Tong Zhang
2021-03-18 15:53 ` Giovanni Cabiddu [this message]
2021-03-18 16:06 ` Giovanni Cabiddu
2021-03-18 16:21 ` [PATCH v4 0/2] crypto: qat: fix couple crashes duing error handling Tong Zhang
2021-03-18 16:21 ` [PATCH v4 1/2] crypto: qat - don't release uninitialized resources Tong Zhang
2021-03-18 16:21 ` [PATCH v4 2/2] crypto: qat: ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-18 17:17 ` Giovanni Cabiddu
2021-03-19 3:39 ` [PATCH v5 0/2] crypto: qat - fix couple crashes duing error handling Tong Zhang
2021-03-19 3:39 ` [PATCH v5 1/2] crypto: qat - don't release uninitialized resources Tong Zhang
2021-03-19 3:40 ` [PATCH v5 2/2] crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-26 9:31 ` [PATCH v5 0/2] crypto: qat - fix couple crashes duing error handling Herbert Xu
2021-03-19 3:41 ` [PATCH v4 2/2] crypto: qat: ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-18 16:22 ` [PATCH v3 1/2] crypto: qat - dont release uninitialized resources Tong Zhang
2021-03-12 16:22 ` [PATCH v3 2/2] crypto: qat: ADF_STATUS_PF_RUNNING should be set after adf_dev_init Tong Zhang
2021-03-18 16:03 ` Giovanni Cabiddu
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=YFN3X6q8dzEaUp27@silpixa00400314 \
--to=giovanni.cabiddu@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=fiona.trahe@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=wojciech.ziemba@intel.com \
--cc=ztong0001@gmail.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