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: Thu, 22 Sep 2016 09:44:20 +0900 From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> To: Matt Fleming <matt@...eblueprint.co.uk> Cc: Petr Mladek <pmladek@...e.com>, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, Byungchul Park <byungchul.park@....com>, Frederic Weisbecker <fweisbec@...il.com>, Luca Abeni <luca.abeni@...tn.it>, Rik van Riel <riel@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, Wanpeng Li <wanpeng.li@...mail.com>, Yuyang Du <yuyang.du@...el.com>, Jan Kara <jack@...e.cz>, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, linux-kernel@...r.kernel.org, Mel Gorman <mgorman@...hsingularity.net>, Mike Galbraith <umgwanakikbuti@...il.com> Subject: Re: [PATCH v2 7/7] sched/core: Add debug code to catch missing update_rq_clock() Hello, On (09/21/16 20:08), Matt Fleming wrote: > On Wed, 21 Sep, at 05:58:27PM, Petr Mladek wrote: > > > > I am not sure how the above call chain is realistic. But adding > > WARN_ON() into the scheduler paths is risky in general. > > It's not clear to me why this should be the case. WARN_ON() calls have > existed in the scheduler paths since forever. > > If the new async printk patches make that impossible then surely they > need fixing, not the scheduler? it's not specific to async printk, because printk already invokes scheduler via semaphore up(). -ss
Powered by blists - more mailing lists