From: Jason Cooper <jason@lakedaemon.net>
To: Stephan Mueller <smueller@chronox.de>,
Grant Likely <grant.likely@secretlab.ca>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel crypto API interface specification
Date: Thu, 16 Oct 2014 11:06:05 -0400 [thread overview]
Message-ID: <20141016150604.GK17447@titan.lakedaemon.net> (raw)
In-Reply-To: <20141016132501.GI17447@titan.lakedaemon.net>
On Thu, Oct 16, 2014 at 09:25:01AM -0400, Jason Cooper wrote:
> + Grant, Geert,
>
> Stephan has created some great example code for both the kernel crypto
> API and the userspace crypto API. As examples tend to bitrot, I was
> wondering if the code could serve as test code. Then it would have a
> triple role: API regression testing, crypto test suite, and reference
> implementation.
>
> Original patch is here:
>
> https://lkml.kernel.org/r/7502136.9BkWHTZ0th@myon.chronox.de
>
> On Thu, Oct 16, 2014 at 09:19:08AM +0200, Stephan Mueller wrote:
> > Am Mittwoch, 15. Oktober 2014, 13:58:00 schrieb Jason Cooper:
> > > On Tue, Oct 14, 2014 at 09:46:50PM +0200, Stephan Mueller wrote:
...
> > > Perhaps the userspace API example should be a separate file with this
> > > text at the top? Seems odd having it at the end. Also, if you copied
> > > it from cryptsetup, is the copyright info correct?
> >
> > I did not copy it from cryptsetup. I only used it as a basis, especially with
> > the data structure handling in _kcapi_cipher_crypt. But you are right, I
> > changed the license for the user space by taking the cryptsetup license.
>
> Ok. It looks like Geert and Grant took part in the kernel test
> unconference, so I'm adding them to the Cc. I hope they can give us
> some pointers as to where we could hook in this code. Then we can
> simply refer to it from the userspace API document.
tools/testing/selftests/crypto would be a good location for the example
code in the next version of this patch. Make sure to take a look at
tools/testing/selftests/README.txt.
thx,
Jason.
next prev parent reply other threads:[~2014-10-16 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 19:46 [PATCH] kernel crypto API interface specification Stephan Mueller
2014-10-14 20:00 ` Stephan Mueller
2014-10-15 17:58 ` Jason Cooper
2014-10-16 7:19 ` Stephan Mueller
2014-10-16 13:25 ` Jason Cooper
2014-10-16 13:29 ` Jason Cooper
2014-10-16 15:06 ` Jason Cooper [this message]
2014-10-16 16:50 ` Stephan Mueller
2014-10-16 17:42 ` Jason Cooper
2014-10-16 13:10 ` Herbert Xu
2014-10-31 3:01 ` Marek Vasut
2014-10-31 7:23 ` Herbert Xu
2014-10-31 9:09 ` Marek Vasut
2014-10-31 13:46 ` Stephan Mueller
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=20141016150604.GK17447@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).