From: Chenghai Huang <huangchenghai2@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<liulongfang@huawei.com>, <qianweili@huawei.com>,
<wangzhou1@hisilicon.com>, <linwenkai6@hisilicon.com>
Subject: [PATCH 0/4] crypto: hisilicon - fix several issues in QM and SEC drivers
Date: Fri, 11 Sep 2026 18:29:38 +0800 [thread overview]
Message-ID: <20260911102942.387778-1-huangchenghai2@huawei.com> (raw)
This series fixes several issues in the Hisilicon QM and SEC drivers:
1.fix the devm_kcalloc() argument order in qm_pre_store_caps().
2.fix scheduling while atomic in the SEC AEAD soft fallback, which is
reachable with the backlog spinlock held.
3.fix a memory leak in hisi_qm_sort_devices() on the kzalloc() failure
path.
4.use GFP_KERNEL instead of GFP_ATOMIC in hisi_qm_memory_init(), which
runs in process context.
Wenkai Lin (4):
crypto: hisilicon/qm - fix devm_kcalloc argument order
crypto: hisilicon/sec2 - fix scheduling while atomic in aead soft
fallback
crypto: hisilicon/qm - fix memory leak in hisi_qm_sort_devices
crypto: hisilicon/qm - fix GFP flag inconsistency in
hisi_qm_memory_init
drivers/crypto/hisilicon/qm.c | 9 ++++++---
drivers/crypto/hisilicon/sec2/sec_crypto.c | 2 +-
2 files changed, 7 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-11 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 10:29 Chenghai Huang [this message]
2026-09-11 10:29 ` [PATCH 1/4] crypto: hisilicon/qm - fix devm_kcalloc argument order Chenghai Huang
2026-09-11 10:29 ` [PATCH 2/4] crypto: hisilicon/sec2 - fix scheduling while atomic in aead soft fallback Chenghai Huang
2026-09-11 10:29 ` [PATCH 3/4] crypto: hisilicon/qm - fix memory leak in hisi_qm_sort_devices Chenghai Huang
2026-09-11 10:29 ` [PATCH 4/4] crypto: hisilicon/qm - fix GFP flag inconsistency in hisi_qm_memory_init Chenghai Huang
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=20260911102942.387778-1-huangchenghai2@huawei.com \
--to=huangchenghai2@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linwenkai6@hisilicon.com \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=wangzhou1@hisilicon.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