> apparently not triggering, since it could be that Debian's initrd > might cause some other uncaught recursion loop if we don't drive this > problem determination to root cause. Agreed - and there are all sorts of obscure and wonderful other ways to trip this up which need the detector (AF_UNIX modular and doing a syslog for example). > > That's why I still think it's a good thing, to connect the core tty > > devices to their dev_t handler internally, before we init all the > > other drivers and run userspace. > > Um, how early? (/me searches lkml.org for the original patch). Ah, > OK, you want to do it postcore.... There may actually be a problem > with that, because it looks like vtconsole_class_init (which is > currently run as a postcore initcall) really wants to happen before > the tty layer initializes itself. So moving tty into postcore could > potentially run into problems, depending on whether vt.c's or > tty_io.c's initcalls are run first. Its playing with fire and doing so to paper over a completely different problem. The recursion detector is generic and should be sufficient. If it isn't then it needs improving to be generic, sufficient and working. -- 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
