From: "T, Pratham" <t-pratham@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Francis, Sebin" <sebin.francis@ti.com>,
"Chawdhry, Manorit" <m-chawdhry@ti.com>,
"Bajjuri, Praneeth" <praneeth@ti.com>,
"Mahaveer, Vishal" <vishalm@ti.com>
Subject: Re: [PATCH v11 00/15] Fix several issues in DTHEv2 driver
Date: Sat, 7 Nov 2026 15:26:50 +0000 [thread overview]
Message-ID: <0fe68821-c8e2-4418-8820-f3340bb8a0dc@ti.com> (raw)
In-Reply-To: <20261107145618.2349562-1-t-pratham@ti.com>
On 07-11-2026 20:26, T, Pratham wrote:
> 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 fifth 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 [1].
>
> One of the issues had already been flagged by kernel test bot and a fix
> sent on the list by Mert [2].
>
> I included this patch in this series with minor edits. Then the Sashiko
> review page for [2] had more comments [3]
>
> 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>
> ---
I see that the patches do not apply cleanly. This is my fault for still
being on 7.3 when 7.4-rc1 is tagged :/
Will rebase, resolve conflicts and resend.
--
Regards
T Pratham <t-pratham@ti.com>
prev parent reply other threads:[~2026-11-07 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 14:56 T Pratham
2026-11-07 14:56 ` [PATCH v11 01/15] crypto: ti - Use list_first_entry_or_null() in dthe_get_dev() T Pratham
2026-11-07 14:56 ` [PATCH v11 02/15] crypto: ti - Fix spinlock inconsistency in DTHEv2 T Pratham
2026-11-07 14:56 ` [PATCH v11 03/15] crypto: ti - Fix potential memory corruption on highmem pages T Pratham
2026-11-07 14:56 ` [PATCH v11 04/15] crypto: ti - Fix use-after-free of dev_data on DTHEv2 driver removal T Pratham
2026-11-07 14:56 ` [PATCH v11 05/15] crypto: ti - Trim scatterlists to correct length in AES T Pratham
2026-11-07 14:56 ` [PATCH v11 06/15] crypto: ti - Align buffers to cacheline for DMA T Pratham
2026-11-07 14:56 ` [PATCH v11 07/15] crypto: ti - Separate padding buffer for src and dst T Pratham
2026-11-07 14:56 ` [PATCH v11 08/15] crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AES T Pratham
2026-11-07 14:56 ` [PATCH v11 09/15] crypto: ti - Validate sg_nents_for_len() return value in DTHEv2 AEAD T Pratham
2026-11-07 14:56 ` [PATCH v11 10/15] crypto: ti - Terminate DMA on all error paths in AES to clear descriptors T Pratham
2026-11-07 14:56 ` [PATCH v11 11/15] crypto: ti - Terminate DMA on all error paths in AEAD " T Pratham
2026-11-07 14:56 ` [PATCH v11 12/15] crypto: ti - Do AEAD software fallback on only ENOMEM T Pratham
2026-11-07 14:56 ` [PATCH v11 13/15] crypto: ti - Correct AEAD tag operations against dma cache invalidation T Pratham
2026-11-07 14:56 ` [PATCH v11 14/15] crypto: ti - Change lengths in AES to u64 to avoid potential overflows T Pratham
2026-11-07 14:56 ` [PATCH v11 15/15] crypto: ti - Change lengths in AEAD " T Pratham
2026-11-07 15:26 ` T, Pratham [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=0fe68821-c8e2-4418-8820-f3340bb8a0dc@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
all inboxes | Powered by JetHome®