From: Christoph Hellwig <hch@lst.de>
To: Israel Rukshin <israelr@nvidia.com>
Cc: Linux-block <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Eric Biggers <ebiggers@kernel.org>,
Nitzan Carmi <nitzanc@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH 0/1 RFC] block: Add ioctl for setting default inline crypto key
Date: Thu, 21 Jul 2022 14:44:26 +0200 [thread overview]
Message-ID: <20220721124426.GA20555@lst.de> (raw)
In-Reply-To: <1658316391-13472-1-git-send-email-israelr@nvidia.com>
On Wed, Jul 20, 2022 at 02:26:30PM +0300, Israel Rukshin wrote:
> Hi Jens/Christoph/Eric
>
> I am working to add support for inline encryption/decryption
> at storage protocols like nvmf over RDMA.
What would that be? nvmf over RDMA suggest on-the-wire transport
encryption, which really is a different think that what fscrypt
and blk-crypto deal with. NVMe has a Key per I/O TP, which is
still waiting for the messy TCG counter part, but as far as I
can tell it is in many ways designed to more or less intentionally
not fit the fscrypt model.
prev parent reply other threads:[~2022-07-21 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 11:26 [PATCH 0/1 RFC] block: Add ioctl for setting default inline crypto key Israel Rukshin
2022-07-20 11:26 ` [PATCH 1/1] block: Add support for setting inline encryption key per block device Israel Rukshin
2022-07-21 6:49 ` [dm-devel] " Eric Biggers
2022-07-21 6:49 ` Eric Biggers
2022-07-21 12:54 ` [dm-devel] " Christoph Hellwig
2022-07-21 12:54 ` Christoph Hellwig
2022-07-22 8:20 ` [dm-devel] " Milan Broz
2022-07-22 8:20 ` Milan Broz
2022-07-26 2:40 ` Daniil Lunev
2022-07-26 2:40 ` Daniil Lunev
2022-07-21 12:51 ` Christoph Hellwig
2022-07-26 0:42 ` Eric Biggers
2022-07-28 16:26 ` Israel Rukshin
2022-07-21 12:44 ` Christoph Hellwig [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=20220721124426.GA20555@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=ebiggers@kernel.org \
--cc=israelr@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=nitzanc@nvidia.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 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.