On Fri, Jul 10, 2026 at 08:54:40PM -0400, Eric Biggers wrote: > > So what is the minimum SG entry length alignment this can result in? > Once that get misaligned enough, crypto_skcipher_encrypt() and > crypto_skcipher_decrypt() start allocating bounce buffers internally. > That code has no mempool fallback and can fail with ENOMEM.
I'm not the one introducing ENOMEM consideration here. Indeed, patch 2 in this series addresses this very thing ahead of what I'm asking for. > I think you'll need to take the limitations of crypto_skcipher into > account. See the comment above CRYPTO_ALG_ALLOCATES_MEMORY. The block layer's queue limits is the single source of truth for what the backing device at any layer can accept. If you've some constraints that are not appropriately described there, then let's fix that.
