From: Changwei Zou <changwei.zou@canonical.com>
To: stephane.debusne@cynove.com
Cc: changwei.zou@canonical.com, davem@davemloft.net,
herbert@gondor.apana.org.au, jeffbarnes@linux.microsoft.com,
horia.geanta@nxp.com, iuliana.prodan@nxp.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas@wunner.de, martin.kepplinger-novakovic@ginzinger.com,
pankaj.gupta@nxp.com, sahil.malhotra@nxp.com,
sahil.malhotra@oss.nxp.com
Subject: Re: [PATCH v2 2/2] crypto: caam - Use bounce buffer for unaligned RSA destination buffers
Date: Sat, 17 Oct 2026 21:20:47 +1100 [thread overview]
Message-ID: <20261017102047.333792-1-changwei.zou@canonical.com> (raw)
In-Reply-To: <20261017081417.2775186-1-stephane.debusne@cynove.com>
Hi Stephane,
Thank you very much for your help with testing the patch.
In fact, I had previously submitted another patch to fix the bug on the caller side:
https://lore.kernel.org/all/20260731024446.786329-1-changwei.zou@canonical.com/
However, Herbert pointed out:
"In the Crypto API we don't ask the user to provide aligned data.
In general it's the driver's responsibility to ensure proper alignment."
https://lore.kernel.org/all/am2UMhd5CAhDiKBF@gondor.apana.org.au/
Therefore, I later switched to a driver-side solution.
I'll include your Tested-by tag when I submit the next version.
Thanks.
next prev parent reply other threads:[~2026-10-17 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 21:01 [PATCH v2 0/2] crypto: caam - Fix RSA destination buffer handling Changwei Zou
2026-10-04 21:01 ` [PATCH v2 1/2] crypto: caam - Fix wrong unmap operations Changwei Zou
2026-10-04 21:02 ` [PATCH v2 2/2] crypto: caam - Use bounce buffer for unaligned RSA destination buffers Changwei Zou
2026-10-17 8:14 ` Stephane Debusne
2026-10-17 10:20 ` Changwei Zou [this message]
2026-10-17 15:39 ` Stephane Debusne
2026-10-08 7:38 ` [PATCH v2 0/2] crypto: caam - Fix RSA destination buffer handling Herbert Xu
2026-10-20 3:21 ` Changwei Zou
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=20261017102047.333792-1-changwei.zou@canonical.com \
--to=changwei.zou@canonical.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=martin.kepplinger-novakovic@ginzinger.com \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@nxp.com \
--cc=sahil.malhotra@oss.nxp.com \
--cc=stephane.debusne@cynove.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
all inboxes | Powered by JetHome®