| 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
| ||
|
Message-ID: <20090106022551.GB1099402@hiwaay.net> Date: Mon, 5 Jan 2009 20:25:51 -0600 From: Chris Adams <cmadams@...aay.net> To: john stultz-lkml <johnstul.lkml@...il.com> Cc: Linas Vepstas <linasvepstas@...il.com>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de> Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 Once upon a time, john stultz-lkml <johnstul.lkml@...il.com> said: > Grrrr. This has bit us a few times since the "no printk while holding > the xtime lock" restriction was added. I didn't see that documented anywhere, so my patch adds a comment to that effect. > Thomas: Do you think this warrents adding a check to the printk path > to make sure the xtime lock isn't held? This way we can at least get a > warning when someone accidentally adds a printk or calls a function > that does while holding the xtime_lock. I'm no kernel locking or scheduling (or anything else) expert, but if printk can check to see if xtime_lock is held, can it skip trying to wake klogd (so messages still get logged, just maybe not quite as fast)? Is there anything else that will wake klogd later? -- Chris Adams <cmadams@...aay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- 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