From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Bharat Bhushan <bbhushan2@marvell.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Sasha Levin <sashal@kernel.org>,
bbrezillon@kernel.org, arno@natisbad.org, schalla@marvell.com,
davem@davemloft.net, ndabilpuram@marvell.com,
masahiroy@kernel.org, alobakin@pm.me, tj@kernel.org,
linux-crypto@vger.kernel.org
Subject: [PATCH AUTOSEL 6.6 12/19] crypto: octeontx2 - Fix cptvf driver cleanup
Date: Mon, 15 Jan 2024 19:23:47 -0500 [thread overview]
Message-ID: <20240116002413.215163-12-sashal@kernel.org> (raw)
In-Reply-To: <20240116002413.215163-1-sashal@kernel.org>
From: Bharat Bhushan <bbhushan2@marvell.com>
[ Upstream commit c480a421a4faf693c38e60b0fe6e554c9a3fee02 ]
This patch fixes following cleanup issues:
- Missing instruction queue free on cleanup. This
will lead to memory leak.
- lfs->lfs_num is set to zero before cleanup, which
will lead to improper cleanup.
Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/crypto/marvell/octeontx2/otx2_cptlf.c | 6 ++++--
drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c | 3 +++
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/marvell/octeontx2/otx2_cptlf.c b/drivers/crypto/marvell/octeontx2/otx2_cptlf.c
index 6edd27ff8c4e..e4bd3f030cec 100644
--- a/drivers/crypto/marvell/octeontx2/otx2_cptlf.c
+++ b/drivers/crypto/marvell/octeontx2/otx2_cptlf.c
@@ -419,8 +419,8 @@ int otx2_cptlf_init(struct otx2_cptlfs_info *lfs, u8 eng_grp_mask, int pri,
return 0;
free_iq:
- otx2_cpt_free_instruction_queues(lfs);
cptlf_hw_cleanup(lfs);
+ otx2_cpt_free_instruction_queues(lfs);
detach_rsrcs:
otx2_cpt_detach_rsrcs_msg(lfs);
clear_lfs_num:
@@ -431,11 +431,13 @@ EXPORT_SYMBOL_NS_GPL(otx2_cptlf_init, CRYPTO_DEV_OCTEONTX2_CPT);
void otx2_cptlf_shutdown(struct otx2_cptlfs_info *lfs)
{
- lfs->lfs_num = 0;
/* Cleanup LFs hardware side */
cptlf_hw_cleanup(lfs);
+ /* Free instruction queues */
+ otx2_cpt_free_instruction_queues(lfs);
/* Send request to detach LFs */
otx2_cpt_detach_rsrcs_msg(lfs);
+ lfs->lfs_num = 0;
}
EXPORT_SYMBOL_NS_GPL(otx2_cptlf_shutdown, CRYPTO_DEV_OCTEONTX2_CPT);
diff --git a/drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c b/drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c
index bac729c885f9..215a1b17b6ce 100644
--- a/drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c
+++ b/drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c
@@ -249,8 +249,11 @@ static void cptvf_lf_shutdown(struct otx2_cptlfs_info *lfs)
otx2_cptlf_unregister_interrupts(lfs);
/* Cleanup LFs software side */
lf_sw_cleanup(lfs);
+ /* Free instruction queues */
+ otx2_cpt_free_instruction_queues(lfs);
/* Send request to detach LFs */
otx2_cpt_detach_rsrcs_msg(lfs);
+ lfs->lfs_num = 0;
}
static int cptvf_lf_init(struct otx2_cptvf_dev *cptvf)
--
2.43.0
next prev parent reply other threads:[~2024-01-16 0:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 0:23 [PATCH AUTOSEL 6.6 01/19] FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 02/19] UBSAN: array-index-out-of-bounds in dtSplitRoot Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 03/19] jfs: fix slab-out-of-bounds Read in dtSearch Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 04/19] jfs: fix array-index-out-of-bounds in dbAdjTree Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 05/19] jfs: fix uaf in jfs_evict_inode Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 06/19] jfs: fix shift-out-of-bounds in dbJoin Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 07/19] hwrng: starfive - Fix dev_err_probe return error Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 08/19] crypto: p10-aes-gcm - Avoid -Wstringop-overflow warnings Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 09/19] pstore/ram: Fix crash when setting number of cpus to an odd number Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 10/19] erofs: fix up compacted indexes for block size < 4096 Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 11/19] crypto: starfive - Fix dev_err_probe return error Sasha Levin
2024-01-16 0:23 ` Sasha Levin [this message]
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 13/19] erofs: fix ztailpacking for subpage compressed blocks Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 14/19] crypto: stm32/crc32 - fix parsing list of devices Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 15/19] afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu() Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 16/19] afs: fix the usage of read_seqbegin_or_lock() in afs_find_server*() Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 17/19] rxrpc_find_service_conn_rcu: fix the usage of read_seqbegin_or_lock() Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 18/19] gfs2: Refcounting fix in gfs2_thaw_super Sasha Levin
2024-01-16 0:23 ` [PATCH AUTOSEL 6.6 19/19] jfs: fix array-index-out-of-bounds in diNewExt Sasha Levin
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=20240116002413.215163-12-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=alobakin@pm.me \
--cc=arno@natisbad.org \
--cc=bbhushan2@marvell.com \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.com \
--cc=stable@vger.kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox