On Sun, Feb 16, 2014 at 10:21 PM, Marco d'Itri <md@xxxxxxxx> wrote: > On Feb 17, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote: > >> > Do you know if the upstream modprobe has the fixes (or plan) to >> > recognize soft dependencies? I was under the impression that it >> > is the case. >> Marco CC'd... > I only maintain the Debian package, but Lucas should know. The way the softdep is declared e.g. in crc32 pretty much broke the concept of softdep that we had before: it was intended to pass dependencies we should try to load, but not bail out if they failed. For softdeps coming from kernel it means: "this is a dependency, but I can't express it in terms of symbols, so consider XXXX the module I depend on". The problem is that depmod has no knowledge of softdeps, only modprobe, which means the dependency loop check is done only while loading a module, not while generating modules.dep. I have a pending patch to make modprobe consider the softdep coming from kernel, but I think it isn't ideal... I'll take a deeper look on this issue this week. Lucas De Marchi -- 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
