From: "boojin.kim" <boojin.kim@samsung.com>
Cc: 'Herbert Xu' <herbert@gondor.apana.org.au>,
"'David S. Miller'" <davem@davemloft.net>,
'Eric Biggers' <ebiggers@kernel.org>,
"'Theodore Y. Ts'o'" <tytso@mit.edu>, 'Chao Yu' <chao@kernel.org>,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
'Andreas Dilger' <adilger.kernel@dilger.ca>'Theodore Ts'o'
<tytso@mit.edu>,
dm-devel@redhat.com, 'Mike Snitzer' <snitzer@redhat.com>,
'Alasdair Kergon' <agk@redhat.com>,
'Jens Axboe' <axboe@kernel.dk>,
'Krzysztof Kozlowski' <krzk@kernel.org>,
'Kukjin Kim' <kgene@kernel.org>,
'Jaehoon Chung' <jh80.chung@samsung.com>,
'Ulf Hansson' <ulf.hansson@linaro.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-samsung-soc
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Wed, 28 Aug 2019 11:20:53 +0900 [thread overview]
Message-ID: <009301d55d47$38606400$a9212c00$@samsung.com> (raw)
In-Reply-To: CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com
On Tue, Aug 27, 2019 at 05:33:33PM +0900, boojin.kim wrote:
>
> Hi Boojin,
>
> I think the important thing to realize here is that there are a large
> number of hardware devices for which the keyslot manager *is* needed.
> And from the upstream kernel's perspective, supporting two different
> schemes for supporting the inline encryption feature is more
> complexity than just supporting one which is general enough to support
> a wider variety of hardware devices.
>
> If you want somethig which is only good for the hardware platform you
> are charged to support, that's fine if it's only going to be in a
> Samsung-specific kernel. But if your goal is to get something that
> works upstream, especially if it requires changes in core layers of
> the kernel, it's important that it's general enough to support most,
> if not all, if the hardware devices in the industry.
>
> Regards,
I understood your reply.
But, Please consider the diskcipher isn't just for FMP.
The UFS in Samsung SoC also has UFS ICE. This UFS ICE can be registered
as an algorithm of diskcipher like FMP.
Following is my opinion to introduce diskcipher.
I think the common feature of ICE like FMP and UFS ICE,
is 'exposing cipher text to storage".
And, Crypto test is also important for ICE. Diskcipher supports
the common feature of ICE.
I think specific functions for each ICE such as the key control of UFS ICE
and the writing crypto table of FMP can be processed at algorithm level.
Thanks for your reply.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: "'Theodore Y. Ts'o'" <tytso@mit.edu>
Cc: "'Herbert Xu'" <herbert@gondor.apana.org.au>,
"'David S. Miller'" <davem@davemloft.net>,
"'Eric Biggers'" <ebiggers@kernel.org>,
"'Theodore Y. Ts'o'" <tytso@mit.edu>,
"'Chao Yu'" <chao@kernel.org>,
"'Jaegeuk Kim'" <jaegeuk@kernel.org>,
"'Andreas Dilger'" <adilger.kernel@dilger.ca>,
"'Theodore Ts'o'" <tytso@mit.edu>, <dm-devel@redhat.com>,
"'Mike Snitzer'" <snitzer@redhat.com>,
"'Alasdair Kergon'" <agk@redhat.com>,
"'Jens Axboe'" <axboe@kernel.dk>,
"'Krzysztof Kozlowski'" <krzk@kernel.org>,
"'Kukjin Kim'" <kgene@kernel.org>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
"'Ulf Hansson'" <ulf.hansson@linaro.org>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fscrypt@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-block@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-samsung-soc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Wed, 28 Aug 2019 11:20:53 +0900 [thread overview]
Message-ID: <009301d55d47$38606400$a9212c00$@samsung.com> (raw)
In-Reply-To: CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com
On Tue, Aug 27, 2019 at 05:33:33PM +0900, boojin.kim wrote:
>
> Hi Boojin,
>
> I think the important thing to realize here is that there are a large
> number of hardware devices for which the keyslot manager *is* needed.
> And from the upstream kernel's perspective, supporting two different
> schemes for supporting the inline encryption feature is more
> complexity than just supporting one which is general enough to support
> a wider variety of hardware devices.
>
> If you want somethig which is only good for the hardware platform you
> are charged to support, that's fine if it's only going to be in a
> Samsung-specific kernel. But if your goal is to get something that
> works upstream, especially if it requires changes in core layers of
> the kernel, it's important that it's general enough to support most,
> if not all, if the hardware devices in the industry.
>
> Regards,
I understood your reply.
But, Please consider the diskcipher isn't just for FMP.
The UFS in Samsung SoC also has UFS ICE. This UFS ICE can be registered
as an algorithm of diskcipher like FMP.
Following is my opinion to introduce diskcipher.
I think the common feature of ICE like FMP and UFS ICE,
is 'exposing cipher text to storage".
And, Crypto test is also important for ICE. Diskcipher supports
the common feature of ICE.
I think specific functions for each ICE such as the key control of UFS ICE
and the writing crypto table of FMP can be processed at algorithm level.
Thanks for your reply.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: "'Theodore Y. Ts'o'" <tytso@mit.edu>
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, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org, 'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
'Jens Axboe' <axboe@kernel.dk>, 'Theodore Ts'o' <tytso@mit.edu>,
linux-mmc@vger.kernel.org, linux-kernel@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: [f2fs-dev] [PATCH 5/9] block: support diskcipher
Date: Wed, 28 Aug 2019 11:20:53 +0900 [thread overview]
Message-ID: <009301d55d47$38606400$a9212c00$@samsung.com> (raw)
In-Reply-To: CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com
On Tue, Aug 27, 2019 at 05:33:33PM +0900, boojin.kim wrote:
>
> Hi Boojin,
>
> I think the important thing to realize here is that there are a large
> number of hardware devices for which the keyslot manager *is* needed.
> And from the upstream kernel's perspective, supporting two different
> schemes for supporting the inline encryption feature is more
> complexity than just supporting one which is general enough to support
> a wider variety of hardware devices.
>
> If you want somethig which is only good for the hardware platform you
> are charged to support, that's fine if it's only going to be in a
> Samsung-specific kernel. But if your goal is to get something that
> works upstream, especially if it requires changes in core layers of
> the kernel, it's important that it's general enough to support most,
> if not all, if the hardware devices in the industry.
>
> Regards,
I understood your reply.
But, Please consider the diskcipher isn't just for FMP.
The UFS in Samsung SoC also has UFS ICE. This UFS ICE can be registered
as an algorithm of diskcipher like FMP.
Following is my opinion to introduce diskcipher.
I think the common feature of ICE like FMP and UFS ICE,
is 'exposing cipher text to storage".
And, Crypto test is also important for ICE. Diskcipher supports
the common feature of ICE.
I think specific functions for each ICE such as the key control of UFS ICE
and the writing crypto table of FMP can be processed at algorithm level.
Thanks for your reply.
Boojin Kim.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: "'Theodore Y. Ts'o'" <tytso@mit.edu>
Cc: 'Herbert Xu' <herbert@gondor.apana.org.au>,
"'David S. Miller'" <davem@davemloft.net>,
'Eric Biggers' <ebiggers@kernel.org>,
"'Theodore Y. Ts'o' <tytso@mit.edu>,
'Chao Yu' <chao@kernel.org>,
'Jaegeuk Kim' " <jaegeuk@kernel.org>,
'Andreas Dilger' <adilger.kernel@dilger.ca>,
dm-devel@redhat.com, 'Mike Snitzer' <snitzer@redhat.com>,
'Alasdair Kergon' <agk@redhat.com>,
'Jens Axboe' <axboe@kernel.dk>,
'Krzysztof Kozlowski' <krzk@kernel.org>,
'Kukjin Kim' <kgene@kernel.org>,
'Jaehoon Chung' <jh80.chung@samsung.com>,
"'Ulf Hansson' <ulf.hansson@linaro.org>,
<linux-crypto@vger.kernel.org>," <linux-kernel@vger.kernel.org>,
linux-fscrypt@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.netlinux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Wed, 28 Aug 2019 11:20:53 +0900 [thread overview]
Message-ID: <009301d55d47$38606400$a9212c00$@samsung.com> (raw)
In-Reply-To: CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com
On Tue, Aug 27, 2019 at 05:33:33PM +0900, boojin.kim wrote:
>
> Hi Boojin,
>
> I think the important thing to realize here is that there are a large
> number of hardware devices for which the keyslot manager *is* needed.
> And from the upstream kernel's perspective, supporting two different
> schemes for supporting the inline encryption feature is more
> complexity than just supporting one which is general enough to support
> a wider variety of hardware devices.
>
> If you want somethig which is only good for the hardware platform you
> are charged to support, that's fine if it's only going to be in a
> Samsung-specific kernel. But if your goal is to get something that
> works upstream, especially if it requires changes in core layers of
> the kernel, it's important that it's general enough to support most,
> if not all, if the hardware devices in the industry.
>
> Regards,
I understood your reply.
But, Please consider the diskcipher isn't just for FMP.
The UFS in Samsung SoC also has UFS ICE. This UFS ICE can be registered
as an algorithm of diskcipher like FMP.
Following is my opinion to introduce diskcipher.
I think the common feature of ICE like FMP and UFS ICE,
is 'exposing cipher text to storage".
And, Crypto test is also important for ICE. Diskcipher supports
the common feature of ICE.
I think specific functions for each ICE such as the key control of UFS ICE
and the writing crypto table of FMP can be processed at algorithm level.
Thanks for your reply.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: "'Theodore Y. Ts'o'" <tytso@mit.edu>
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-block@vger.kernel.org, linux-fscrypt@vger.kernel.org,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
'Jens Axboe' <axboe@kernel.dk>, 'Theodore Ts'o' <tytso@mit.edu>,
linux-mmc@vger.kernel.org, linux-kernel@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, 28 Aug 2019 11:20:53 +0900 [thread overview]
Message-ID: <009301d55d47$38606400$a9212c00$@samsung.com> (raw)
In-Reply-To: CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com
On Tue, Aug 27, 2019 at 05:33:33PM +0900, boojin.kim wrote:
>
> Hi Boojin,
>
> I think the important thing to realize here is that there are a large
> number of hardware devices for which the keyslot manager *is* needed.
> And from the upstream kernel's perspective, supporting two different
> schemes for supporting the inline encryption feature is more
> complexity than just supporting one which is general enough to support
> a wider variety of hardware devices.
>
> If you want somethig which is only good for the hardware platform you
> are charged to support, that's fine if it's only going to be in a
> Samsung-specific kernel. But if your goal is to get something that
> works upstream, especially if it requires changes in core layers of
> the kernel, it's important that it's general enough to support most,
> if not all, if the hardware devices in the industry.
>
> Regards,
I understood your reply.
But, Please consider the diskcipher isn't just for FMP.
The UFS in Samsung SoC also has UFS ICE. This UFS ICE can be registered
as an algorithm of diskcipher like FMP.
Following is my opinion to introduce diskcipher.
I think the common feature of ICE like FMP and UFS ICE,
is 'exposing cipher text to storage".
And, Crypto test is also important for ICE. Diskcipher supports
the common feature of ICE.
I think specific functions for each ICE such as the key control of UFS ICE
and the writing crypto table of FMP can be processed at algorithm level.
Thanks for your reply.
Boojin Kim.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2019-08-28 2:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com>
2019-08-28 2:20 ` boojin.kim [this message]
2019-08-28 2:20 ` [PATCH 5/9] block: support diskcipher boojin.kim
2019-08-28 2:20 ` boojin.kim
2019-08-28 2:20 ` [f2fs-dev] " boojin.kim
2019-08-28 2:20 ` boojin.kim
[not found] <CGME20190827083334epcas2p115d479190b9a72c886f66569add78203@epcas2p1.samsung.com>
2019-08-27 8:33 ` boojin.kim
2019-08-27 8:33 ` boojin.kim
2019-08-27 8:33 ` boojin.kim
2019-08-27 8:33 ` boojin.kim
2019-08-27 16:40 ` Theodore Y. Ts'o
2019-08-27 16:40 ` Theodore Y. Ts'o
2019-08-27 16:40 ` Theodore Y. Ts'o
[not found] <CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com>
2019-08-22 0:54 ` boojin.kim
2019-08-22 0:54 ` boojin.kim
2019-08-22 0:54 ` boojin.kim
2019-08-22 0:54 ` boojin.kim
[not found] <CGME20190821064226epcas2p2835b8a9084988b79107e54abfc5e7dab@epcas2p2.samsung.com>
2019-08-21 6:42 ` boojin.kim
2019-08-21 6:42 ` boojin.kim
2019-08-21 6:42 ` boojin.kim
2019-08-21 6:42 ` boojin.kim
2019-08-21 12:09 ` Jens Axboe
2019-08-21 12:09 ` Jens Axboe
2019-08-21 12:09 ` Jens Axboe
2019-08-23 2:35 ` Satya Tangirala
2019-08-23 2:35 ` Satya Tangirala
2019-08-23 2:35 ` Satya Tangirala
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='009301d55d47$38606400$a9212c00$@samsung.com' \
--to=boojin.kim@samsung.com \
--cc=adilger.kernel@dilger.ca \
--cc=chao@kernel.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jaegeuk@kernel.org \
--cc=tytso@mit.edu \
/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.