From: Jens Axboe <axboe@kernel.dk>
To: "boojin.kim" <boojin.kim@samsung.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: 'Ulf Hansson' <ulf.hansson@linaro.org>,
'Mike Snitzer' <snitzer@redhat.com>,
dm-devel@redhat.com, 'Andreas Dilger' <adilger.kernel@dilger.ca>,
'Alasdair Kergon' <agk@redhat.com>,
'Eric Biggers' <ebiggers@kernel.org>,
linux-samsung-soc@vger.kernel.org,
'Herbert Xu' <herbert@gondor.apana.org.au>,
'Krzysztof Kozlowski' <krzk@kernel.org>,
'Jaehoon Chung' <jh80.chung@samsung.com>,
'Kukjin Kim' <kgene@kernel.org>,
linux-ext4@vger.kernel.org, 'Chao Yu' <chao@kernel.org>,
linux-fscrypt@vger.kernel.org, 'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"'Theodore Y. Ts'o'" <tytso@mit.edu>,
linux-mmc@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"'David S. Miller'" <davem@davemloft.net>
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Wed, 21 Aug 2019 06:09:50 -0600 [thread overview]
Message-ID: <6ea5e5db-4dd4-719f-3b3e-b89099636ea6@kernel.dk> (raw)
In-Reply-To: <004101d557eb$98b00060$ca100120$@samsung.com>
On 8/21/19 12:42 AM, boojin.kim wrote:
> This patch supports crypto information to be maintained via BIO
> and passed to the storage driver.
>
> To do this, 'bi_aux_private', 'REQ_CYPTE' and 'bi_dun' are added
> to the block layer.
>
> 'bi_aux_private' is added for loading additional private information into
> BIO.
> 'REQ_CRYPT' is added to distinguish that bi_aux_private is being used
> for diskcipher.
> F2FS among encryption users uses DUN(device unit number) as
> the IV(initial vector) for cryptographic operations.
> DUN is stored in 'bi_dun' of bi_iter as a specific value for each BIO.
>
> Before attempting to merge the two BIOs, the operation is also added to
> verify that the crypto information contained in two BIOs is consistent.
This isn't going to happen. With this, and the inline encryption
proposed by Google, we'll bloat the bio even more. At least the Google
approach didn't include bio iter changes as well.
Please work it out between yourselves so we can have a single, clean
abstraction that works for both.
--
Jens Axboe
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-21 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190821064226epcas2p2835b8a9084988b79107e54abfc5e7dab@epcas2p2.samsung.com>
2019-08-21 6:42 ` [PATCH 5/9] block: support diskcipher boojin.kim
2019-08-21 12:09 ` Jens Axboe [this message]
2019-08-23 2:35 ` Satya Tangirala
[not found] <CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com>
2019-08-22 0:54 ` boojin.kim
[not found] <CGME20190827083334epcas2p115d479190b9a72c886f66569add78203@epcas2p1.samsung.com>
2019-08-27 8:33 ` boojin.kim
2019-08-27 16:40 ` Theodore Y. Ts'o
[not found] <CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com>
2019-08-28 2:20 ` boojin.kim
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=6ea5e5db-4dd4-719f-3b3e-b89099636ea6@kernel.dk \
--to=axboe@kernel.dk \
--cc=adilger.kernel@dilger.ca \
--cc=agk@redhat.com \
--cc=boojin.kim@samsung.com \
--cc=chao@kernel.org \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jaegeuk@kernel.org \
--cc=jh80.chung@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@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-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
--cc=ulf.hansson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).