From: T Pratham <t-pratham@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: T Pratham <t-pratham@ti.com>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Sebin Francis <sebin.francis@ti.com>,
"Manorit Chawdhry" <m-chawdhry@ti.com>,
Vishal Mahaveer <vishalm@ti.com>,
"Praneeth Bajjuri" <praneeth@ti.com>
Subject: [PATCH v2 0/7] Fix several issues in DTHEv2 driver
Date: Thu, 27 Aug 2026 18:53:11 +0530 [thread overview]
Message-ID: <20260827132318.613876-1-t-pratham@ti.com> (raw)
This series fixes a handful of independent and mostly benign till now
issues in the DTHEv2 driver which were flagged by bots and AI agents.
Except for the fourth patch in this series which was found in an
internal testing.
The Sashiko review on DTHEv2 hashing driver patch series v5 pointed out
some pre-existing issues which needed to be fixed.
https://sashiko.dev/#/patchset/20260807110501.975130-1-t-pratham%40ti.com
One of the issues had already been flagged by kernel test bot and a fix
sent on the list by Mert:
https://lore.kernel.org/all/20260613085858.32580-1-mertsftl@gmail.com/
I included this patch in this series with minor edits. Then the Sashiko
review page for this had more comments:
https://sashiko.dev/#/patchset/20260613085858.32580-1-mertsftl%40gmail.com
Overall this resulted in a bunch of fixes patches which would have
deviated the DTHEv2 hashing driver series had they been included with
it. So I clubbed them together in a new patch series which is this.
Signed-off-by: T Pratham <t-pratham@ti.com>
---
Changelog:
v2:
- Fixes based on Sashiko comments
Link to previous versions:
v1: https://lore.kernel.org/all/20260827105711.527182-1-t-pratham@ti.com/
---
Mert Seftali (1):
crypto: ti - Use list_first_entry_or_null() in dthe_get_dev()
T Pratham (6):
crypto: ti - Fix potential deadlock bug in DTHEv2
crypto: ti - Fix potential memory corruption on highmem pages
crypto: ti - Trim scatterlists to correct length in AES
crypto: ti - Fix use-after-free of dev_data on DTHEv2 driver removal
crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AES
crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AEAD
drivers/crypto/ti/dthev2-aes.c | 184 ++++++++++++++++++------------
drivers/crypto/ti/dthev2-common.c | 32 +++++-
drivers/crypto/ti/dthev2-common.h | 7 +-
3 files changed, 140 insertions(+), 83 deletions(-)
--
2.34.1
next reply other threads:[~2026-08-27 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 13:23 T Pratham [this message]
2026-08-27 13:23 ` [PATCH v2 1/7] crypto: ti - Use list_first_entry_or_null() in dthe_get_dev() T Pratham
2026-08-27 13:23 ` [PATCH v2 2/7] crypto: ti - Fix potential deadlock bug in DTHEv2 T Pratham
2026-08-27 13:23 ` [PATCH v2 3/7] crypto: ti - Fix potential memory corruption on highmem pages T Pratham
2026-08-27 13:23 ` [PATCH v2 4/7] crypto: ti - Trim scatterlists to correct length in AES T Pratham
2026-08-27 13:23 ` [PATCH v2 5/7] crypto: ti - Fix use-after-free of dev_data on DTHEv2 driver removal T Pratham
2026-08-27 13:23 ` [PATCH v2 6/7] crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AES T Pratham
2026-08-27 13:23 ` [PATCH v2 7/7] crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AEAD T Pratham
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=20260827132318.613876-1-t-pratham@ti.com \
--to=t-pratham@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=praneeth@ti.com \
--cc=sebin.francis@ti.com \
--cc=vishalm@ti.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;
as well as URLs for NNTP newsgroup(s).