On Wed, Dec 01, 2021 at 07:51:25PM -0800, Kees Cook wrote: > > But the scomp API appears to be "internal only": > > include/crypto/internal/scompress.h:static inline int crypto_scomp_decompress(struct crypto_scomp *tfm, > > What's the correct API calling sequence to do a simple decompress? OK we haven't wired up scomp to users because there was no user to start with. So if you like you can create it just as we did for shash. The question becomes do you want to restrict your use-case to synchronous-only algorithms, i.e., you will never be able to access offload devices that support compression? Typically this would only make sense if you process a very small amount of data, but this seems counter-intuitive with compression (it does make sense with hashing where we often hash just 16 bytes). Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
