Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ralf Lici <ralf@mandelbit.com>
Cc: linux-crypto@vger.kernel.org, Antoine Tenart <atenart@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH crypto 2/2] crypto: safexcel - Map AEAD buffers with accurate DMA directions
Date: Thu, 8 Oct 2026 18:53:18 +1100	[thread overview]
Message-ID: <asdL7rQTM5nSTIH5@gondor.apana.org.au> (raw)
In-Reply-To: <20260928102502.266108-1-ralf@mandelbit.com>

On Mon, Sep 28, 2026 at 12:25:00PM +0200, Ralf Lici wrote:
>
> For an out-of-place request, the caller may have already populated the
> reserved destination AAD area. The AEAD API says that this area will not
> be written by the cipher operation:

That's what I was asking.  Which caller is doing this and thus
would be broken without your patch?

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2026-10-08  7:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 11:32 [PATCH crypto 0/2] crypto: safexcel: fix AEAD DMA mapping and cleanup Ralf Lici
2026-09-15 11:32 ` [PATCH crypto 1/2] crypto: safexcel - Avoid unmapping failed DMA mappings Ralf Lici
2026-09-15 11:32 ` [PATCH crypto 2/2] crypto: safexcel - Map AEAD buffers with accurate DMA directions Ralf Lici
2026-09-23  5:30   ` Herbert Xu
2026-09-23  7:26     ` Ralf Lici
2026-09-23  8:32       ` Herbert Xu
2026-09-23  9:13         ` Ralf Lici
2026-09-28  5:12           ` Herbert Xu
2026-09-28 10:25             ` Ralf Lici
2026-10-08  7:53               ` Herbert Xu [this message]
2026-10-08  8:21                 ` Ralf Lici

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=asdL7rQTM5nSTIH5@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@mandelbit.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