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, 14 Feb 2017 19:29:56 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Sergey Senozhatsky <sergey.senozhatsky@...il.com> Cc: Tony Lindgren <tony@...mide.com>, Petr Mladek <pmladek@...e.com>, Steven Rostedt <rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, "Rafael J. Wysocki" <rjw@...ysocki.net>, linux-pm@...r.kernel.org, John Stultz <john.stultz@...aro.org> Subject: Re: Regression in next with use printk_safe buffers in printk On Wed, Feb 15, 2017 at 01:56:45AM +0900, Sergey Senozhatsky wrote: > that crossed my mind, but I kinda assumed that we do printk() from > under tk_core using sched fair, and rt_runtime_lock is from sched rt. That's all true; lockdep doesn't care :-) All it knows is that at some point those locks nest.
Powered by blists - more mailing lists