Linux cryptographic layer development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: brandon@ifup.org, linux-crypto@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: Fixing gave up waiting for init of module libcrc32c.
Date: Fri, 19 Mar 2010 19:46:12 -0700 (PDT)	[thread overview]
Message-ID: <20100319.194612.226782074.davem@davemloft.net> (raw)
In-Reply-To: <20100320010849.GA30654@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sat, 20 Mar 2010 09:08:49 +0800

> On Sat, Mar 20, 2010 at 09:01:15AM +0800, Herbert Xu wrote:
>>
>> IIRC modprobe(8) in user-space is supposed to load all dependencies
>> prior to loading the main module.  So something must've gone wrong
>> before bnx2/bnx2x was loaded.  Please strace it to see why libcrc32c
>> wasn't loaded successfully before the kernel ever saw bnx2/bnx2x.
> 
> In fact I just tried it on my machine and modprobe bnx2x correctly
> loaded libcrc32c + crc32c before loading bnx2x (you don't need the
> hardware, it'll stay loaded).  My kernel is 2.6.33-rc8.
> 
> I suspect it's a user-space problem.  I'm using module-init-tools
> 3.4-1 from Debian.

Even if userland "does" this, nothing stops another thread
from rmmod'ing the dependency in between the modloads.

We have to handle this case properly in the kernel, no matter
what.

  reply	other threads:[~2010-03-20  2:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 23:40 Fixing gave up waiting for init of module libcrc32c Brandon Philips
2010-03-20  1:01 ` Herbert Xu
2010-03-20  1:08   ` Herbert Xu
2010-03-20  2:46     ` David Miller [this message]
2010-03-20  3:45       ` Herbert Xu
2010-03-20  4:21     ` Brandon Philips
2010-03-20  4:24       ` Herbert Xu
2010-03-20  5:23         ` David Miller
2010-03-20 12:29           ` Herbert Xu
2010-03-20 13:16             ` Neil Horman
2010-03-29 23:06             ` Rusty Russell
2010-03-31 19:03               ` Brandon Philips
2010-03-31 23:25                 ` Rusty Russell
2010-03-30 16:50             ` Brandon Philips
2010-03-30 17:47               ` Kay Sievers

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=20100319.194612.226782074.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brandon@ifup.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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