Re: [BUG] crypto: caam - RSA encrypt doesn't always complete new data in out_buf

[Lukas Wunner]

On Tue, Feb 24, 2026 at 04:09:51PM +0000, Kepplinger-Novakovic Martin wrote:
> Am Dienstag, dem 24.02.2026 um 16:04 +0100 schrieb Lukas Wunner:
> > On Tue, Feb 24, 2026 at 02:17:22PM +0000, Kepplinger-Novakovic Martin wrote:
> > > This works until v6.6 and fails after ("crypto: ahash - optimize
> > > performance when wrapping shash")
> > > but too much has happened that I could revert one and I might be wrong
> > > with that commit even.
> > 
> > It would be good if you could bisect to exactly pinpoint the offending
> > commit.
> 
> I know v6.6 worked. v6.7 showed
> [    2.978722] caam_jr 2142000.jr: 40000013: DECO: desc idx 0: Header Error.
> Invalid length or parity, or certain other problems.

Well there are 18404 commits between v6.6 and v6.7, so 14 or 15 steps
should be sufficient to find the culprit with git bisect.

It's quite doubtful that 2f1f34c1bf7b ("crypto: ahash - optimize
performance when wrapping shash") has anything to do with it.
It doesn't touch asymmetric crypto code.  If you absolutely
positively think it's the culprit, "git checkout 2f1f34c1bf7b^"
plus compile would confirm that.

> I can try to narrow this down a bit later.

I really recommend starting with git bisect now, not doing it later.
It's the most efficient use of your time.

Thanks,

Lukas