All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org
Subject: Trouble with non modular ciphers
Date: Thu, 31 Jan 2008 10:21:24 +0100	[thread overview]
Message-ID: <200801311021.24240.ak@suse.de> (raw)


FYI -- with a linus git kernel of yesterday or so I ran into a problem where 
one cipher module (CBC) was compiled in and the rest modular. dm_crypt 
could not resolve the cipher module until I turned it into a module.
I don't remember if cryptomanager was modular or not.

I don't have the exact configuration anymore unfortunately, but just
wanted to report the problem.

Also I found that cryptomanager is quite unhappy when CONFIG_KMOD
is not defined. Perhaps it should Kconfig select it?

-Andi

             reply	other threads:[~2008-01-31  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  9:21 Andi Kleen [this message]
2008-01-31 12:48 ` Trouble with non modular ciphers Sebastian Siewior
2008-01-31 12:49   ` Andi Kleen
2008-01-31 13:12     ` Sebastian Siewior
2008-02-01  0:12 ` Herbert Xu
2008-02-04 18:56   ` Async Linux NETKEY (IPSec Stack) Loc Ho
2008-02-04 22:37     ` Herbert Xu

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=200801311021.24240.ak@suse.de \
    --to=ak@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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 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.