From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Stephan Mueller <smueller@chronox.de>
Subject: Re: [PATCH 1/2] crypto: export crypto_alg_list and rwsem
Date: Thu, 13 Aug 2015 16:30:31 +0900 [thread overview]
Message-ID: <20150813073031.GC13352@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20150813063823.GA20830@gondor.apana.org.au>
On Thu, Aug 13, 2015 at 02:38:23PM +0800, Herbert Xu wrote:
> On Thu, Aug 13, 2015 at 03:37:55PM +0900, Joonsoo Kim wrote:
> >
> > Is there any way to access netlink interface and get the output from
> > kernel-side? I'd like to show information through
> > "/sys/block/zramX/comp_algorithm", because some user program can be
> > broken if we change output of userspace exposed interface.
>
> You could simply deprecate that interface but keep it for existing
> algorithms. Any new algorithms can then be queried through the
> crypto_user interface.
>
> The other option is to have a defined list of algorithms which is
> independent of the crypto API. For example, have a look at what
> IPsec does in net/xfrm/xfrm_algo.c. IPsec needs its own list
> because they come with annotations.
Hmm... they looks suboptimal.
How about introducing new functions to search supported algorithm in
kernel-side? As crypto API is used in more places, this interface
would be requested more. Defined list weaken the advantage of strong
point of generic crypto API.
Thanks.
next prev parent reply other threads:[~2015-08-13 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 2:24 [PATCH 1/2] crypto: export crypto_alg_list and rwsem Joonsoo Kim
2015-08-13 2:24 ` [PATCH 2/2] zram: use crypto API to compress the page Joonsoo Kim
2015-08-13 3:51 ` Sergey Senozhatsky
2015-08-13 5:21 ` Sergey Senozhatsky
2015-08-13 7:19 ` Joonsoo Kim
2015-08-13 7:32 ` Herbert Xu
2015-08-13 7:42 ` Joonsoo Kim
2015-08-13 3:19 ` [PATCH 1/2] crypto: export crypto_alg_list and rwsem Herbert Xu
2015-08-13 6:37 ` Joonsoo Kim
2015-08-13 6:38 ` Herbert Xu
2015-08-13 7:30 ` Joonsoo Kim [this message]
2015-08-13 7:29 ` Herbert Xu
2015-08-13 7:43 ` Joonsoo 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=20150813073031.GC13352@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=smueller@chronox.de \
/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