On Thu, Jan 19, 2012 at 1:28 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Jan 19, 2012 at 01:26:30PM +0100, Francis Moreau wrote: >> On Thu, Jan 19, 2012 at 12:58 PM, Herbert Xu >> <herbert@xxxxxxxxxxxxxxxxxxx> wrote: >> > On Thu, Jan 19, 2012 at 09:10:48AM +0100, Francis Moreau wrote: >> >> >> >> How things are supposed to work when : >> >> >> >> - crc32c module is not loaded >> >> - libcrc32c module is not loaded >> >> - btrfs is not loaded >> >> >> >> and I issue: "modprobe btrfs" ? >> > >> > When libcrc32c is loaded it'll automatically load crc32c through >> > the Crypto API. >> > >> >> Did you try ? > > Yes it works on my machine. > Ok, It's acutally the user space tools which are confused: they don't have a way to track the dependency therefore crc32c is not included in my initrd. I'm wondering how this could be fixed... I could hard code the dependency in userspace but it looks like an ugly workaround. 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
