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, 18 Feb 2016 12:39:06 +0200 From: Joonas Lahtinen <joonas.lahtinen@...ux.intel.com> To: Peter Zijlstra <peterz@...radead.org> Cc: Oleg Nesterov <oleg@...hat.com>, Intel graphics driver community testing & development <intel-gfx@...ts.freedesktop.org>, Linux kernel development <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...nel.org>, David Hildenbrand <dahi@...ux.vnet.ibm.com>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, "Gautham R. Shenoy" <ego@...ux.vnet.ibm.com>, Chris Wilson <chris@...is-wilson.co.uk> Subject: Re: [Intel-gfx] [PATCH] [RFC] kernel/cpu: Use lockref for online CPU reference counting On ke, 2016-02-17 at 17:37 +0100, Peter Zijlstra wrote: > On Wed, Feb 17, 2016 at 05:33:51PM +0100, Daniel Vetter wrote: > > On Wed, Feb 17, 2016 at 05:14:57PM +0100, Peter Zijlstra wrote: > > > On Wed, Feb 17, 2016 at 05:13:21PM +0100, Daniel Vetter wrote: > > > > And for context we're hitting this on CI in a bunch of our machines, which > > > > > > What's CI ? > > > > Continuous integration, aka our own farm of machines dedicated to running > > i915.ko testcases. Kinda like 0day (it does pre-merge testing on the m-l > > and also post-merge on our own little integration tree), but for just the > > graphics team and our needs. > > So what patch triggered this new issue? Did cpufreq change or what? It appeared right after enabling lockdep debugging on the continuous integration system. So we do not have a history of it not being there. Taking an another look at my code, it could indeed end up in double- wait-looping scenario if suspend and initialization was performed simultaneously (it had a couple of other bugs too, fixed in v2). Strange thing is, I think that should have been caught by cpuhp_lock_* lockdep tracking. So I'll move the discussion to linux-pm list to change the CPUfreq code. Thanks for the comments. Regards, Joonas -- Joonas Lahtinen Open Source Technology Center Intel Corporation
Powered by blists - more mailing lists