From: Eric Biggers <ebiggers@kernel.org>
To: "zheng.gong" <zheng.gong@samsung.com>
Cc: linux-scsi@vger.kernel.org, avri.altman@wdc.com,
bvanassche@acm.org, quic_cang@quicinc.com,
alim.akhtar@samsung.com, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] scsi: ufs: Add crypto_keyslot_remap support
Date: Thu, 27 Nov 2025 14:24:29 -0800 [thread overview]
Message-ID: <20251127222429.GB2977@sol> (raw)
In-Reply-To: <20251127070704.2935390-1-zheng.gong@samsung.com>
On Thu, Nov 27, 2025 at 03:06:57PM +0800, zheng.gong wrote:
> This patch series adds support for platform-specific crypto keyslot remapping
> in the UFS host driver, enabling secure inline encryption in multi-domain
> environments (e.g., VMs).
>
> The first patch introduces a new variant operation:
> ufs_hba_variant_ops::crypto_keyslot_remap
> which allows platforms to adjust the keyslot index at request submission time.
>
> The second patch adds a test module (CONFIG_SCSI_UFS_CRYPTO_TEST) to
> demonstrate how the new hook is used — by applying a fixed offset to simulate
> domain-specific keyslot layout. This patch series is in response to feedback from Eric on the v1 submission,
> where he noted that the new callback needed to be used to make sense. Just a demonstration
> of the new callback is included in this patch series.
There has to be a real user, not just a useless example module.
Perhaps you intend for this functionality to be used in ufs-exynos.c?
But you haven't sent any corresponding patch.
- Eric
next prev parent reply other threads:[~2025-11-27 22:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251112030559epcas5p13358e7b05ca6b39688530b9c8178527e@epcas5p1.samsung.com>
[not found] ` <20251112030524.3545394-1-zheng.gong@samsung.com>
2025-11-12 3:05 ` [PATCH 1/1] scsi: ufs: crypto: Add ufs_hba_variant_ops::crypto_keyslot_remap zheng.gong
2025-11-12 3:10 ` Eric Biggers
2025-11-27 7:06 ` [PATCH v2 0/2] scsi: ufs: Add crypto_keyslot_remap support zheng.gong
2025-11-27 7:06 ` [PATCH v2 1/2] scsi: ufs: crypto: Add ufs_hba_variant_ops::crypto_keyslot_remap zheng.gong
2025-11-27 7:06 ` [PATCH v2 2/2] scsi: ufs: Add crypto keyslot remapping test module zheng.gong
2025-11-27 22:24 ` Eric Biggers [this message]
2025-11-28 3:37 ` [PATCH v3 0/1] scsi: ufs: Add crypto_keyslot_remap variant op zheng.gong
2025-11-28 3:37 ` [PATCH v3 1/1] scsi: ufs: crypto: Add ufs_hba_variant_ops::crypto_keyslot_remap zheng.gong
2025-11-28 3:47 ` [PATCH v3 0/1] scsi: ufs: Add crypto_keyslot_remap variant op Eric Biggers
2026-01-29 3:10 ` [PATCH v4 0/3] scsi: ufs: Add crypto_keyslot_remap support zheng.gong
2026-01-29 3:10 ` [PATCH v4 1/3] scsi: ufs: crypto: Add ufs_hba_variant_ops::crypto_keyslot_remap zheng.gong
2026-01-29 16:43 ` Bart Van Assche
2026-01-29 3:10 ` [PATCH v4 2/3] scsi: ufs: exynos: Support crypto keyslot remapping via DT zheng.gong
2026-01-29 3:10 ` [PATCH v4 3/3] dt-bindings: ufs: Add binding for ufs-keyslot-offset zheng.gong
2026-01-29 3:31 ` [PATCH v4 0/3] scsi: ufs: Add crypto_keyslot_remap support Eric Biggers
2026-01-29 6:17 ` zheng.gong
2026-01-29 7:42 ` Eric Biggers
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=20251127222429.GB2977@sol \
--to=ebiggers@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.com \
--cc=zheng.gong@samsung.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