All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linlin Zhang <linlin.zhang@oss.qualcomm.com>
Cc: virtio-dev@lists.linux.dev, stefanha@redhat.com,
	ebiggers@kernel.org, neeraj.soni@oss.qualcomm.com
Subject: Re: [PATCH v3 0/2] virtio-blk: Add inline encryption support
Date: Wed, 14 Oct 2026 05:48:50 -0400	[thread overview]
Message-ID: <20261014054146-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260913161628.368484-1-linlin.zhang@oss.qualcomm.com>

First, this needs to be reposed to virtio-comment.

On Sun, Sep 13, 2026 at 09:16:13AM -0700, Linlin Zhang wrote:
> From: linlzhan <linlin.zhang@oss.qualcomm.com>
> 
> This series adds virtio-blk inline encryption support for devices backed
> by storage hardware with an inline crypto engine.
> 
> The protocol exposes device capabilities such as keyslot count, maximum
> DUN size, and supported key types. Encrypted requests identify a
> provisioned keyslot and carry a 256-bit DUN. Key management and crypto
> capability discovery use the block device control virtqueue.
> 
> The control virtqueue is defined as a generic framework so that its
> buffer layout and queue placement are independent of any particular
> control command. Inline encryption then builds on this framework with
> explicit crypto command formats, capability validation, and keyslot
> state semantics.
> 
> All key related operatios are handled in the control virtqueue, and
> the crypto I/O request is handled in the request queue.
> 
> For background on inline encryption in UFS and eMMC storage, see:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/block/inline-encryption.rst


What I worry about, is that after all the effort, virtio
crypto is being deprecated upstream.

So please tell us:
- how do we know this will be different?
- what was the response in upstream linux?
- what are some plans for use of this?

I also feel this needs a security section, given how
security sensitive this can be. E.g. is this safe to
enable for confidential computing guests?

Thanks!

> changes in v3:
>  - Add a control virtqueue
>  - Move key program/evict/derive_sw_secret/generate/prepare/import to
>    the control virtqueue
>  - Add the driver and device requirements for the request in the control
>    virtqueue
>  - Extend DUN in crypto message to a fixed four-element array of 64-bit
>    fields 
> 
> changes in v2:
>  - Revmove virtualization-specific terminology
>  - Move MUST sentence to the device/driver normative section
>  - Add explicit rejection for CRYPTO request if IE feature bit
>    isn't negociated
>  - Modify the support list of crypto modes and the definition of
>    the size of the crypto modes buffer
> ---
> 
> linlzhan (2):
>   virtio-blk: Add the control virtqueue
>   virtio-blk: Add inline encryption support
> 
>  device-types/blk/description.tex | 457 +++++++++++++++++++++++++++++--
>  1 file changed, 441 insertions(+), 16 deletions(-)
> 
> -- 
> 2.34.1
> 


      parent reply	other threads:[~2026-10-14  9:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 16:16 [PATCH v3 0/2] virtio-blk: Add inline encryption support Linlin Zhang
2026-09-13 16:16 ` [PATCH v3 1/2] virtio-blk: Add the control virtqueue Linlin Zhang
2026-09-17 20:16   ` Stefan Hajnoczi
2026-09-22 11:10     ` Linlin Zhang
2026-10-14  9:43   ` Michael S. Tsirkin
2026-09-13 16:16 ` [PATCH v3 2/2] virtio-blk: Add inline encryption support Linlin Zhang
2026-09-17 21:05   ` Stefan Hajnoczi
2026-09-24  9:32     ` Linlin Zhang
2026-09-17 21:08 ` [PATCH v3 0/2] " Stefan Hajnoczi
2026-09-22  4:29   ` Linlin Zhang
2026-09-22 13:14     ` Stefan Hajnoczi
2026-09-24  9:35       ` Linlin Zhang
2026-09-29 22:46         ` Max Gurtovoy
2026-10-08  9:17           ` Linlin Zhang
2026-10-08 10:15             ` Michael S. Tsirkin
2026-10-09 11:21               ` Linlin Zhang
2026-10-09 12:25                 ` Michael S. Tsirkin
2026-10-10 10:54                   ` Linlin Zhang
2026-10-12 14:51                     ` Linlin Zhang
2026-10-12 22:33                     ` Michael S. Tsirkin
2026-10-13 16:23                       ` Linlin Zhang
2026-10-13 18:08                         ` Michael S. Tsirkin
2026-10-13 19:07                         ` Stefan Hajnoczi
2026-10-12 23:12               ` Max Gurtovoy
2026-10-13 16:23                 ` Linlin Zhang
2026-10-13 18:07                   ` Max Gurtovoy
2026-10-13 18:10                     ` Michael S. Tsirkin
     [not found]                   ` <SJ0PR12MB68060279EA2241FAEB2EDE8CDC9D2@SJ0PR12MB6806.namprd12.prod.outlook.com>
2026-10-14  4:12                     ` Parav Pandit
2026-10-14  8:47                 ` Michael S. Tsirkin
2026-10-14  9:48 ` Michael S. Tsirkin [this message]

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=20261014054146-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=linlin.zhang@oss.qualcomm.com \
    --cc=neeraj.soni@oss.qualcomm.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.