On Wed, Jan 18, 2012 at 1:13 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Jan 18, 2012 at 08:49:13AM +0100, Francis Moreau wrote:
>>
>> > What is the user in question?
>>
>> btrfs
>
> Hmm, why does it need to do crc32c at module init time?
>
What do you mean with "at module init time" ?
My point is:
$ grep btrfs /lib/modules/3.2.1/modules.dep
kernel/fs/btrfs/btrfs.ko: kernel/lib/zlib_deflate/zlib_deflate.ko
kernel/lib/libcrc32c.ko
and
$ grep libcrc32c.ko: /lib/modules/3.2.1-1.1-desktop/modules.dep
kernel/lib/libcrc32c.ko:
So there's no dependency here to 'pull' a crc32c backend, therefore
"crypto_alloc_shash("crc32c", 0, 0)" used by libcrc32c at load time
fails.
Thanks
--
Francis
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
