linux-kernel - Re: [PATCH v2 1/5] crypto:caam - avoid allocating memory at crypto request runtime for skcipher

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230610021835.GB872@sol.localdomain>
Date:   Fri, 9 Jun 2023 19:18:35 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     meenakshi.aggarwal@....com
Cc:     horia.geanta@....com, V.sethi@....com, pankaj.gupta@....com,
        gaurav.jain@....com, herbert@...dor.apana.org.au,
        davem@...emloft.net, linux-crypto@...r.kernel.org,
        linux-kernel@...r.kernel.org, iuliana.prodan@....com
Subject: Re: [PATCH v2 1/5] crypto:caam - avoid allocating memory at crypto
 request runtime for skcipher

On Fri, Jun 09, 2023 at 12:38:38PM +0200, meenakshi.aggarwal@....com wrote:
> If the driver needs more than the 4 entries maximum, the memory
> is dynamically allocated, at runtime.

Again, this is not currently allowed.  Please see my comment on v1:
https://lore.kernel.org/linux-crypto/20230523165503.GA864814@google.com

- Eric