From: Thomas Huth <thuth@redhat.com>
To: Ahsan Atta <ahsan.atta@intel.com>, herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Subject: Re: [PATCH v2] crypto: qat - fix active_devs leak on crypto alg registration failure
Date: Tue, 8 Sep 2026 18:09:03 +0200 [thread overview]
Message-ID: <2fcf19b9-d049-43c8-900a-082377e30edc@redhat.com> (raw)
In-Reply-To: <20260908121013.697443-1-ahsan.atta@intel.com>
On 08/09/2026 14.10, Ahsan Atta wrote:
> adf_dev_start() registered both alg sets in a single condition.
> If qat_algs_register() succeeds but qat_asym_algs_register() fails,
> ADF_STATUS_CRYPTO_ALGS_REGISTERED is left clear, so adf_dev_stop() skips
> qat_algs_unregister(): the skciphers and aeads stay registered with
> active_devs stuck at 1, pinning the module.
>
> Both helpers leak active_devs internally as well - they increment it and
> return without decrementing when a crypto_register_*() call fails, and
> the asym path also leaves the already-registered akcipher behind.
>
> Split the registration in adf_dev_start() so that an asym failure
> unregisters qat_algs, and unwind active_devs (and the akcipher) on the
> error paths of both register helpers. While at it, propagate the error
> code returned by the register helpers instead of a blanket -EFAULT.
>
> Fixes: 9b2f33a1bfcd ("crypto: qat - fix unregistration of crypto algorithms")
> Signed-off-by: Ahsan Atta <ahsan.atta@intel.com>
> Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> ---
> Changes in v2:
> - adf_dev_start(): propagate the error code returned by qat_algs_register()
> and qat_asym_algs_register() instead of returning a blanket -EFAULT.
>
> .../crypto/intel/qat/qat_common/adf_init.c | 24 ++++++++++++-----
> .../crypto/intel/qat/qat_common/qat_algs.c | 15 ++++++-----
> .../intel/qat/qat_common/qat_asym_algs.c | 26 ++++++++++++++-----
> 3 files changed, 45 insertions(+), 20 deletions(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2026-09-08 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 12:10 [PATCH v2] crypto: qat - fix active_devs leak on crypto alg registration failure Ahsan Atta
2026-09-08 16:09 ` Thomas Huth [this message]
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=2fcf19b9-d049-43c8-900a-082377e30edc@redhat.com \
--to=thuth@redhat.com \
--cc=ahsan.atta@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@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