From: Christoph Hellwig <hch@infradead.org>
To: Satya Tangirala <satyat@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@kernel.org>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org,
Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
Kuohong Wang <kuohong.wang@mediatek.com>,
Kim Boojin <boojin.kim@samsung.com>
Subject: Re: [PATCH v13 00/12] Inline Encryption Support
Date: Fri, 15 May 2020 07:42:24 -0700 [thread overview]
Message-ID: <20200515144224.GA12040@infradead.org> (raw)
In-Reply-To: <20200515122540.GA143740@google.com>
On Fri, May 15, 2020 at 12:25:40PM +0000, Satya Tangirala wrote:
> One of the nice things about the current design is that regardless of what
> request queue an FS sends an encrypted bio to, blk-crypto will be able to handle
> the encryption (whether by using hardware inline encryption, or using the
> blk-crypto-fallback). The FS itself does not need to worry about what the
> request queue is.
True. Which just makes me despise that design with the pointless
fallback even more..
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Satya Tangirala <satyat@google.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>,
Kuohong Wang <kuohong.wang@mediatek.com>,
Kim Boojin <boojin.kim@samsung.com>,
Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v13 00/12] Inline Encryption Support
Date: Fri, 15 May 2020 07:42:24 -0700 [thread overview]
Message-ID: <20200515144224.GA12040@infradead.org> (raw)
In-Reply-To: <20200515122540.GA143740@google.com>
On Fri, May 15, 2020 at 12:25:40PM +0000, Satya Tangirala wrote:
> One of the nice things about the current design is that regardless of what
> request queue an FS sends an encrypted bio to, blk-crypto will be able to handle
> the encryption (whether by using hardware inline encryption, or using the
> blk-crypto-fallback). The FS itself does not need to worry about what the
> request queue is.
True. Which just makes me despise that design with the pointless
fallback even more..
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-05-15 14:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 0:37 [PATCH v13 00/12] Inline Encryption Support Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 01/12] Documentation: Document the blk-crypto framework Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 02/12] block: Keyslot Manager for Inline Encryption Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 03/12] block: Inline encryption support for blk-mq Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 04/12] block: Make blk-integrity preclude hardware inline encryption Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 05/12] block: blk-crypto-fallback for Inline Encryption Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 06/12] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-15 3:55 ` Stanley Chu
2020-05-15 3:55 ` [f2fs-dev] " Stanley Chu
2020-05-14 0:37 ` [PATCH v13 07/12] scsi: ufs: UFS crypto API Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-15 6:35 ` Stanley Chu
2020-05-15 6:35 ` [f2fs-dev] " Stanley Chu
2020-05-14 0:37 ` [PATCH v13 08/12] scsi: ufs: Add inline encryption support to UFS Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 5:12 ` Eric Biggers
2020-05-14 5:12 ` [f2fs-dev] " Eric Biggers
2020-05-15 7:37 ` Stanley Chu
2020-05-15 7:37 ` [f2fs-dev] " Stanley Chu
2020-05-14 0:37 ` [PATCH v13 09/12] fs: introduce SB_INLINECRYPT Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 10/12] fscrypt: add inline encryption support Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-28 21:54 ` Eric Biggers
2020-05-28 21:54 ` [f2fs-dev] " Eric Biggers
2020-06-03 2:07 ` Eric Biggers
2020-06-03 2:07 ` [f2fs-dev] " Eric Biggers
2020-05-14 0:37 ` [PATCH v13 11/12] f2fs: " Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 0:37 ` [PATCH v13 12/12] ext4: " Satya Tangirala
2020-05-14 0:37 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-14 5:10 ` [PATCH v13 00/12] Inline Encryption Support Eric Biggers
2020-05-14 5:10 ` [f2fs-dev] " Eric Biggers
2020-05-14 15:48 ` Jens Axboe
2020-05-14 15:48 ` [f2fs-dev] " Jens Axboe
2020-05-15 7:41 ` Christoph Hellwig
2020-05-15 7:41 ` [f2fs-dev] " Christoph Hellwig
2020-05-15 12:25 ` Satya Tangirala
2020-05-15 12:25 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-05-15 14:42 ` Christoph Hellwig [this message]
2020-05-15 14:42 ` Christoph Hellwig
2020-05-15 17:00 ` Eric Biggers
2020-05-15 17:00 ` [f2fs-dev] " Eric Biggers
2020-05-18 16:50 ` Christoph Hellwig
2020-05-18 16:50 ` [f2fs-dev] " Christoph Hellwig
2020-05-15 1:04 ` Martin K. Petersen
2020-05-15 1:04 ` [f2fs-dev] " Martin K. Petersen
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=20200515144224.GA12040@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bmuthuku@qti.qualcomm.com \
--cc=boojin.kim@samsung.com \
--cc=ebiggers@kernel.org \
--cc=kuohong.wang@mediatek.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyat@google.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.