| 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: Wed, 12 Mar 2014 10:25:36 +0100 From: Peter Zijlstra <peterz@...radead.org> To: John Stultz <john.stultz@...aro.org> Cc: Jiri Bohac <jbohac@...e.cz>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de> Subject: Re: is printk() safe within a timekeeper_seq write section? On Tue, Mar 11, 2014 at 12:29:45PM -0700, John Stultz wrote: > So I don't think I've seen anything like the above in my testing, but it > may just be very hard to get that path to trigger. You have to explicitly enable HRTICK for this to be possible; its disabled by default. -- 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