lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 9 Dec 2008 10:13:32 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Theodore Tso <tytso@....edu> Cc: Kay Sievers <kay.sievers@...y.org>, Evgeniy Polyakov <zbr@...emap.net>, Herbert Xu <herbert@...dor.apana.org.au>, linux-kernel@...r.kernel.org, Linux Crypto Mailing List <linux-crypto@...r.kernel.org> Subject: Re: Runaway loop with the current git. > 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists