From: T Pratham <t-pratham@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Manorit Chawdhry <m-chawdhry@ti.com>,
"Shiva Tripathi" <s-tripathi1@ti.com>
Subject: Re: [PATCH] crypto: ahash - Fix crypto_ahash_import with partial block data
Date: Mon, 24 Nov 2025 15:17:54 +0530 [thread overview]
Message-ID: <890ea55e-c6b7-43ff-b9ca-423bb7fe4979@ti.com> (raw)
In-Reply-To: <aR_6Q4yjEzsQvm4c@gondor.apana.org.au>
On 21/11/25 11:06, Herbert Xu wrote:
> On Thu, Nov 13, 2025 at 07:30:12PM +0530, T Pratham wrote:
>>
> Restore the partial block buffer in crypto_ahash_import by copying
> it. Check whether the partial block buffer exceeds the maximum
> size and return -EOVERFLOW if it does.
>
> Zero the partial block buffer in crypto_ahash_import_core.
>
> Reported-by: T Pratham <t-pratham@ti.com>
> Fixes: 9d7a0ab1c753 ("crypto: ahash - Handle partial blocks in API")
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
This fixes the issue.
Tested-by: T Pratham <t-pratham@ti.com>
--
Regards
T Pratham <t-pratham@ti.com>
next prev parent reply other threads:[~2025-11-24 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 14:00 [BUG 0/2] crypto: ahash - Bugs introduced due to CRYPTO_AHASH_ALG_BLOCK_ONLY T Pratham
2025-11-13 14:00 ` [BUG 1/2] crypto: ahash - import/export fails for algs using CRYPTO_AHASH_ALG_BLOCK_ONLY T Pratham
2025-11-21 5:36 ` [PATCH] crypto: ahash - Fix crypto_ahash_import with partial block data Herbert Xu
2025-11-24 9:47 ` T Pratham [this message]
2025-11-13 14:00 ` [BUG 2/2] crypto: ahash - testmgr false failures with CRYPTO_AHASH_ALG_BLOCK_ONLY T Pratham
2025-11-21 5:54 ` [PATCH] crypto: ahash - Zero positive err value in ahash_update_finish Herbert Xu
2025-11-24 9:50 ` 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=890ea55e-c6b7-43ff-b9ca-423bb7fe4979@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=s-tripathi1@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®