From: Eric Biggers <ebiggers@kernel.org>
To: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org,
abel.vesa@linaro.org, linux-mmc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
Subject: Re: [PATCH v3] mmc: host: sdhci-msm: Add support for wrapped keys
Date: Mon, 29 Dec 2025 14:25:28 -0800 [thread overview]
Message-ID: <20251229222528.GA4684@sol> (raw)
In-Reply-To: <20251229070507.3322149-1-neeraj.soni@oss.qualcomm.com>
On Mon, Dec 29, 2025 at 12:35:07PM +0530, Neeraj Soni wrote:
> Add the wrapped key support for sdhci-msm by implementing the needed
> methods in struct blk_crypto_ll_ops and setting the appropriate flag in
> blk_crypto_profile::key_types_supported.
>
> Tested on SC7280 eMMC variant.
>
> How to test:
>
> Use the "wip-wrapped-keys-2024-12-09" tag from https://github.com/ebiggers/fscryptctl
> and build fscryptctl that supports generating wrapped keys.
Use the official release of fscryptctl from
https://github.com/google/fscryptctl instead. v1.3.0 has wrapped key
support.
Note that the tag you linked to was for an older version of the wrapped
key patches that wasn't compatible with the upstreamed version. So it
isn't plausible that it still works. I'll assume you actually tested a
different version and then just listed the wrong tag in your commit
message. To avoid confusion, I've deleted that old tag.
> Tested-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
> Signed-off-by: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Otherwise this patch looks good.
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
next prev parent reply other threads:[~2025-12-29 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 7:05 [PATCH v3] mmc: host: sdhci-msm: Add support for wrapped keys Neeraj Soni
2025-12-29 13:18 ` Konrad Dybcio
2025-12-30 6:02 ` Neeraj Soni
2025-12-29 22:25 ` Eric Biggers [this message]
2025-12-30 6:06 ` Neeraj Soni
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=20251229222528.GA4684@sol \
--to=ebiggers@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=ulf.hansson@linaro.org \
--cc=wenjia.zhang@oss.qualcomm.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