| 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: <1170262956.9781.117.camel@imap.mvista.com> Date: Wed, 31 Jan 2007 09:02:35 -0800 From: Daniel Walker <dwalker@...sta.com> To: Ingo Molnar <mingo@...e.hu> Cc: akpm@...l.org, linux-kernel@...r.kernel.org, johnstul@...ibm.com, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH 23/23] clocksource tsc: add verify routine On Wed, 2007-01-31 at 13:43 +0100, Ingo Molnar wrote: > * Daniel Walker <dwalker@...sta.com> wrote: > > > I've included this as another user of the clocksource interface. I > > don't see a usage for this across all achitectures. So a fully generic > > version isn't needed. > > well, this implementation is buggy in at least two ways: > > firstly, it allows a circular verification dependency in highres+dyntick > mode between the jiffies and tsc clocksources. In the current implementation, it's only happens if the only clocks that exist are "tsc" and "jiffies" which makes verification impossible anyway .. It's unlikely, but it is possible , the fix is not that complex. > secondly, verification is not done while the system is booting up: Do you know that this is needed ? The current implementation (clocksource watchdog) doesn't fully settle until after device_initcall() .. So boot-up is about 99% complete .. It's trivial to make my version do verification during most of device_initcall() .. Daniel - 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