From: Akhil R <akhilrajeev@nvidia.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-crypto@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Akhil R <akhilrajeev@nvidia.com>
Subject: [PATCH v2 00/10] Tegra Security Engine driver improvements
Date: Tue, 11 Feb 2025 22:47:03 +0530 [thread overview]
Message-ID: <20250211171713.65770-1-akhilrajeev@nvidia.com> (raw)
With the CRYPTO_TEST now being run asynchronously unveiled some
concurrency issues in the Security Engine driver. These were not
caught during functional or fuzz testing as all the tests were run
synchronously.
This patchset contains the fixes for the concurrency issues and few
other improvements identified during the stress-ng and cryptsetup tests.
---
v1->v2:
* Added patch to handle the scenario when keyslots are full
* Added patch to finalize crypto request which was not called in some
error cases.
v1: https://lore.kernel.org/lkml/20241217161207.72921-1-akhilrajeev@nvidia.com/
Akhil R (10):
crypto: tegra: Use separate buffer for setkey
crypto: tegra: Do not use fixed size buffers
crypto: tegra: finalize crypto req on error
crypto: tegra: check return value for hash do_one_req
crypto: tegra: Transfer HASH init function to crypto engine
crypto: tegra: Fix HASH intermediate result handling
crypto: tegra: Fix CMAC intermediate result handling
crypto: tegra: Set IV to NULL explicitly for AES ECB
crypto: tegra: Reserve keyslots to allocate dynamically
crypto: tegra: Use HMAC fallback when keyslots are full
drivers/crypto/tegra/tegra-se-aes.c | 400 ++++++++++++++++++---------
drivers/crypto/tegra/tegra-se-hash.c | 285 ++++++++++++-------
drivers/crypto/tegra/tegra-se-key.c | 27 +-
drivers/crypto/tegra/tegra-se-main.c | 16 +-
drivers/crypto/tegra/tegra-se.h | 39 ++-
5 files changed, 522 insertions(+), 245 deletions(-)
--
2.43.2
next reply other threads:[~2025-02-11 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 17:17 Akhil R [this message]
2025-02-11 17:17 ` [PATCH v2 01/10] crypto: tegra: Use separate buffer for setkey Akhil R
2025-02-11 17:17 ` [PATCH v2 02/10] crypto: tegra: Do not use fixed size buffers Akhil R
2025-02-11 17:17 ` [PATCH v2 03/10] crypto: tegra: finalize crypto req on error Akhil R
2025-02-11 17:17 ` [PATCH v2 04/10] crypto: tegra: check return value for hash do_one_req Akhil R
2025-02-11 17:17 ` [PATCH v2 05/10] crypto: tegra: Transfer HASH init function to crypto engine Akhil R
2025-02-13 7:46 ` kernel test robot
2025-02-11 17:17 ` [PATCH v2 06/10] crypto: tegra: Fix HASH intermediate result handling Akhil R
2025-02-13 4:49 ` kernel test robot
2025-02-13 6:26 ` kernel test robot
2025-02-13 10:04 ` kernel test robot
2025-02-11 17:17 ` [PATCH v2 07/10] crypto: tegra: Fix CMAC " Akhil R
2025-02-11 17:17 ` [PATCH v2 08/10] crypto: tegra: Set IV to NULL explicitly for AES ECB Akhil R
2025-02-11 17:17 ` [PATCH v2 09/10] crypto: tegra: Reserve keyslots to allocate dynamically Akhil R
2025-02-13 8:30 ` kernel test robot
2025-02-11 17:17 ` [PATCH v2 10/10] crypto: tegra: Use HMAC fallback when keyslots are full Akhil R
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=20250211171713.65770-1-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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