Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: 478166@bugs.debian.org, linux-crypto@vger.kernel.org
Subject: Re: linux-image-2.6.24-1-686: airo hang when loading because of aes
Date: Mon, 01 Jun 2009 03:02:50 +0100	[thread overview]
Message-ID: <1243821770.14399.190.camel@deadeye> (raw)

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

matthieu castet <castet.matthieu@free.fr> wrote:
> airo driver hang with 2.6.24-6 on a PIII.
> It seems it it because it need aes crypto.
> It will first try to load padlock-aes, but it fails to load
> Then it load geode_aes which load, and airo hang (airo seems to use
> geode_aes). [1]
[...]

geode_aes is a PCI driver and should be automatically loaded if the PCI
device it handles is present.  However, since it also declares the alias
"aes", when the crypto system attempts to load the "aes" module it may
load this module and then wait for up to a minute for it to initialise
and register the "aes" algorithm.  geode_aes will never do this, since
if there was a suitable device present it would already have been
loaded.

(The padlock modules don't seem to have the same problem because their
module initialisation functions immediately return failure if the CPU
doesn't support.)

I believe geode_aes can be fixed by either (1) removing the MODULE_ALIAS
declaration or (2) making the module initialisation function fail if the
device is not present.  The latter behaviour is generally wrong for PCI
drivers, but this device presumably cannot be hotplugged.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2009-06-01  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  2:02 Ben Hutchings [this message]
2009-06-02  5:12 ` linux-image-2.6.24-1-686: airo hang when loading because of aes Herbert Xu
2009-06-02  8:30   ` Ben Hutchings

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=1243821770.14399.190.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=478166@bugs.debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox