From: Dongsoo Lee <letrhee@nsr.re.kr>
To: 'Eric Biggers' <ebiggers@kernel.org>
Cc: 'Herbert Xu' <herbert@gondor.apana.org.au>,
"'David S. Miller'" <davem@davemloft.net>,
'Jens Axboe' <axboe@kernel.dk>,
"'Theodore Y. Ts'o'" <tytso@mit.edu>,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-crypto@vger.kernel.org, linux-block@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH v3 4/4] fscrypt: Add LEA-256-XTS, LEA-256-CTS support
Date: Fri, 30 Jun 2023 13:45:10 +0900 [thread overview]
Message-ID: <001201d9ab0d$a6ab50b0$f401f210$@nsr.re.kr> (raw)
In-Reply-To: <20230630025914.GB1088@sol.localdomain>
On Thu, Jun 29, 2023 at 19:59:14 -0700, Eric Biggers wrote:
> I don't think that really addresses my comment, due to the second
sentence. I
> understand that you would like to advertise the performance of LEA. But
as I
> mentioned, it's not yet realized in the kernel crypto API, and in the
context of
> fscrypt it won't really bring anything new to the table anyway. For now I
think
> LEA is best described as a "national pride cipher" alongside SM4... Keep
in
> mind, it can always be changed later if new use cases come up.
>
> Could you just omit the documentation update from your patch? I actually
need
> to rework the whole "Encryption modes and usage" section anyway since it's
> growing a bit unwieldy, with 6 different combinations of encryption modes
now
> supported. The information needs to be organized better. It currently
reads
> like a list, and it might be hard for users to understand which setting to
use.
>
> I'll add on a patch that does that and adds the mention of LEA support.
>
> - Eric
Thanks for the feedback.
We'll remove the documentation and submit the next version.
next prev parent reply other threads:[~2023-06-30 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 8:46 [PATCH v3 0/4] crypto: LEA block cipher implementation Dongsoo Lee
2023-06-26 8:47 ` [PATCH v3 1/4] " Dongsoo Lee
2023-06-26 8:47 ` [PATCH v3 2/4] crypto: add LEA testmgr tests Dongsoo Lee
2023-06-26 8:47 ` [PATCH v3 3/4] blk-crypto: Add LEA-256-XTS blk-crypto support Dongsoo Lee
2023-06-26 8:47 ` [PATCH v3 4/4] fscrypt: Add LEA-256-XTS, LEA-256-CTS support Dongsoo Lee
2023-06-28 6:38 ` Eric Biggers
2023-06-29 10:01 ` Dongsoo Lee
2023-06-30 2:59 ` Eric Biggers
2023-06-30 4:45 ` Dongsoo Lee [this message]
2023-06-30 6:59 ` Eric Biggers
2023-06-30 7:53 ` Dongsoo Lee
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='001201d9ab0d$a6ab50b0$f401f210$@nsr.re.kr' \
--to=letrhee@nsr.re.kr \
--cc=axboe@kernel.dk \
--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-crypto@vger.kernel.org \
--cc=linux-fscrypt@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 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).