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, 15 Nov 2017 17:32:41 -0800 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Thomas Gleixner <tglx@...utronix.de> Cc: Mark Salyzyn <salyzyn@...roid.com>, Petr Mladek <pmladek@...e.com>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>, Andrew Morton <akpm@...ux-foundation.org>, Prarit Bhargava <prarit@...hat.com>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Steven Rostedt <rostedt@...dmis.org>, John Stultz <john.stultz@...aro.org> Subject: Re: [GIT pull] printk updates for 4.15 On Wed, Nov 15, 2017 at 4:37 PM, Thomas Gleixner <tglx@...utronix.de> wrote: > > This broke stuff because the historic behaviour was to not advance on > resume and the change caused massive timer expiries right after resume > which confused the hell out of things, because timers fired immediately > which were not expected to fire as they were implicitely relying on suspend > not affecting clock monotonic. Ahh, now that you mention it, I remember that. Things coming to a complete halt because every single X event timer and network timer all firing at resume. If the timer wheel thing doesn't happen any more, I'd still be willing to try it out, but you're right, it might be much worse than I thought. Linus
Powered by blists - more mailing lists