From: "boojin.kim" <boojin.kim@samsung.com>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
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-fscrypt@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-ext4@v
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Thu, 22 Aug 2019 09:54:38 +0900 [thread overview]
Message-ID: <017901d55884$2cbc8f60$8635ae20$@samsung.com> (raw)
In-Reply-To: CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com
On 8/21/19 21:09 AM, Jens Axboe wrote:
> 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.
I'm looking at inline encryption by Google.
I will find compatibility with inline encryption to avoid conflicts
in BIO/F2FS.
And changing bio iter has a benefit for diskcipher.
Without changing bio iter, diskcipher should control(alloc/free) a buffer
to hold a 'bi_dun' variable for every bio.
But changing bio iter is difficult to accept for block layer,
I will modify the diskcipher.
And, as you mentioned, inline encryption by Google has this control.
So I might be able to use it.
Thanks.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: <axboe@kernel.dk>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
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-fscrypt@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <linux-samsung-soc@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: Thu, 22 Aug 2019 09:54:38 +0900 [thread overview]
Message-ID: <017901d55884$2cbc8f60$8635ae20$@samsung.com> (raw)
In-Reply-To: CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com
On 8/21/19 21:09 AM, Jens Axboe wrote:
> 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.
I'm looking at inline encryption by Google.
I will find compatibility with inline encryption to avoid conflicts
in BIO/F2FS.
And changing bio iter has a benefit for diskcipher.
Without changing bio iter, diskcipher should control(alloc/free) a buffer
to hold a 'bi_dun' variable for every bio.
But changing bio iter is difficult to accept for block layer,
I will modify the diskcipher.
And, as you mentioned, inline encryption by Google has this control.
So I might be able to use it.
Thanks.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: <axboe@kernel.dk>, <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, 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-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: Thu, 22 Aug 2019 09:54:38 +0900 [thread overview]
Message-ID: <017901d55884$2cbc8f60$8635ae20$@samsung.com> (raw)
In-Reply-To: CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com
On 8/21/19 21:09 AM, Jens Axboe wrote:
> 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.
I'm looking at inline encryption by Google.
I will find compatibility with inline encryption to avoid conflicts
in BIO/F2FS.
And changing bio iter has a benefit for diskcipher.
Without changing bio iter, diskcipher should control(alloc/free) a buffer
to hold a 'bi_dun' variable for every bio.
But changing bio iter is difficult to accept for block layer,
I will modify the diskcipher.
And, as you mentioned, inline encryption by Google has this control.
So I might be able to use it.
Thanks.
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: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
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>,
'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-fscrypt@vger.kernel.org>,
linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.netlinux-samsung-soc,
linux-arm-kernel@lists.infradead.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 5/9] block: support diskcipher
Date: Thu, 22 Aug 2019 09:54:38 +0900 [thread overview]
Message-ID: <017901d55884$2cbc8f60$8635ae20$@samsung.com> (raw)
In-Reply-To: CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com
On 8/21/19 21:09 AM, Jens Axboe wrote:
> 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.
I'm looking at inline encryption by Google.
I will find compatibility with inline encryption to avoid conflicts
in BIO/F2FS.
And changing bio iter has a benefit for diskcipher.
Without changing bio iter, diskcipher should control(alloc/free) a buffer
to hold a 'bi_dun' variable for every bio.
But changing bio iter is difficult to accept for block layer,
I will modify the diskcipher.
And, as you mentioned, inline encryption by Google has this control.
So I might be able to use it.
Thanks.
Boojin Kim.
WARNING: multiple messages have this Message-ID (diff)
From: "boojin.kim" <boojin.kim@samsung.com>
To: <axboe@kernel.dk>, <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,
'Jens Axboe' <axboe@kernel.dk>, 'Theodore 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: Thu, 22 Aug 2019 09:54:38 +0900 [thread overview]
Message-ID: <017901d55884$2cbc8f60$8635ae20$@samsung.com> (raw)
In-Reply-To: CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com
On 8/21/19 21:09 AM, Jens Axboe wrote:
> 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.
I'm looking at inline encryption by Google.
I will find compatibility with inline encryption to avoid conflicts
in BIO/F2FS.
And changing bio iter has a benefit for diskcipher.
Without changing bio iter, diskcipher should control(alloc/free) a buffer
to hold a 'bi_dun' variable for every bio.
But changing bio iter is difficult to accept for block layer,
I will modify the diskcipher.
And, as you mentioned, inline encryption by Google has this control.
So I might be able to use it.
Thanks.
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-22 0:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190822005438epcas2p337aba06b328cdcdd1549395f0bbcfdbc@epcas2p3.samsung.com>
2019-08-22 0:54 ` boojin.kim [this message]
2019-08-22 0:54 ` [PATCH 5/9] block: support diskcipher boojin.kim
2019-08-22 0:54 ` boojin.kim
2019-08-22 0:54 ` [f2fs-dev] " boojin.kim
2019-08-22 0:54 ` boojin.kim
[not found] <CGME20190828022055epcas2p25525077d0a5a3fa5a2027bac06a10bc1@epcas2p2.samsung.com>
2019-08-28 2:20 ` boojin.kim
2019-08-28 2:20 ` boojin.kim
2019-08-28 2:20 ` 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] <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='017901d55884$2cbc8f60$8635ae20$@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=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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.