From: Jason Cooper <jason@lakedaemon.net>
To: Eric Rost <eric.rost@mybabylon.net>
Cc: gregkh@linuxfoundation.org, jake@lwn.net, antonysaraev@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: skein: Loadable Module Support
Date: Wed, 22 Oct 2014 12:24:49 -0400 [thread overview]
Message-ID: <20141022162449.GZ17447@titan.lakedaemon.net> (raw)
In-Reply-To: <1413993266.11638.1.camel@mybabylon.net>
On Wed, Oct 22, 2014 at 10:54:26AM -0500, Eric Rost wrote:
> On Wed, 2014-10-22 at 11:10 -0400, Jason Cooper wrote:
> > At some point, Eric Rost wrote:
...
> > > diff --git a/drivers/staging/skein/Makefile b/drivers/staging/skein/Makefile
> > > index a14aadd..1be01fe 100644
> > > --- a/drivers/staging/skein/Makefile
> > > +++ b/drivers/staging/skein/Makefile
> > > @@ -5,5 +5,11 @@ obj-$(CONFIG_CRYPTO_SKEIN) += skein.o \
> > > skein_api.o \
> > > skein_block.o
> > >
> > > +obj-$(CONFIG_CRYPTO_SKEIN_256) += skein256_generic.o
> > > +
> > > +obj-$(CONFIG_CRYPTO_SKEIN_512) += skein512_generic.o
> > > +
> > > +obj-$(CONFIG_CRYPTO_SKEIN_1024) += skein1024_generic.o
> > > +
> >
> > This isn't really doing what we want. You'll have loadable modules, but
> > the actual code will still be built into the kernel.
> >
> > > obj-$(CONFIG_CRYPTO_THREEFISH) += threefish_block.o \
> > > threefish_api.o
> > > diff --git a/drivers/staging/skein/skein.c b/drivers/staging/skein/skein.c
> > > index 8cc8358..2138e22 100644
> > > --- a/drivers/staging/skein/skein.c
> > > +++ b/drivers/staging/skein/skein.c
> > > @@ -11,6 +11,7 @@
> > > #define SKEIN_PORT_CODE /* instantiate any code in skein_port.h */
> > >
> > > #include <linux/string.h> /* get the memcpy/memset functions */
> > > +#include <linux/export.h>
> > > #include "skein.h" /* get the Skein API definitions */
> > > #include "skein_iv.h" /* get precomputed IVs */
> > > #include "skein_block.h"
> > > @@ -73,6 +74,7 @@ int skein_256_init(struct skein_256_ctx *ctx, size_t hash_bit_len)
> > >
> > > return SKEIN_SUCCESS;
> > > }
> > > +EXPORT_SYMBOL(skein_256_init);
> >
> > Once the above is corrected, these shouldn't be necessary.
> >
> Will give it a whirl, I was having problems with undefined symbols at
> linking even when I was building it as one module, but it may have been
> something else
Try just changing CRYPTO_SKEIN to a tri-state, and adding your
skein_generic.o to the obj-$(CONFIG_CRYPTO_SKEIN) list.
You'll probably have to collapse CRYPTO_THREEFISH into CRYPTO_SKEIN for
now. Let's get the crypto API registration proper first, them we can
focus on the loadable module bit.
thx,
Jason.
prev parent reply other threads:[~2014-10-22 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 14:44 Eric Rost
2014-10-22 15:10 ` Jason Cooper
2014-10-22 15:54 ` Eric Rost
2014-10-22 16:24 ` Jason Cooper [this message]
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=20141022162449.GZ17447@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=antonysaraev@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric.rost@mybabylon.net \
--cc=gregkh@linuxfoundation.org \
--cc=jake@lwn.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®