[PATCH v2] printk: fix one circular lockdep warning about console_lock

2014-03-19 Thread jiel
From: Jane Li This patch tries to fix a warning about possible circular locking dependency. If do in following sequence: enter suspend -> resume -> plug-out CPUx (echo 0 > cpux/online) lockdep will show warning as following: == [ INFO: p

[PATCH] printk: fix one circular lockdep warning about console_lock

2014-02-10 Thread jiel
From: Jane Li This patch tries to fix a warning about possible circular locking dependency. If do in following sequence: enter suspend -> resume -> plug-out CPUx (echo 0 > cpux/online) lockdep will show warning as following: == [ INFO: p

[PATCH v4] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled

2014-01-03 Thread jiel
From: Jane Li When a CPU is hot removed we'll cancel all the delayed work items via gov_cancel_work(). Sometimes the delayed work function determines that it should adjust the delay for all other CPUs that the policy is managing. If this scenario occurs, the canceling CPU will cancel its own work

[PATCH v3] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled

2014-01-02 Thread jiel
From: Jane Li When a CPU is hot removed we'll cancel all the delayed work items via gov_cancel_work(). Sometimes the delayed work function determines that it should adjust the delay for all other CPUs that the policy is managing. If this scenario occurs, the canceling CPU will cancel its own work

[PATCH v2] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled

2014-01-01 Thread jiel
From: Jane Li When a CPU is hot removed we'll cancel all the delayed work items via gov_cancel_work(). Sometimes the delayed work function determines that it should adjust the delay for all other CPUs that the policy is managing. If this scenario occurs, the canceling CPU will cancel its own work

[PATCH] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled

2013-12-27 Thread jiel
From: Jane Li When a CPU is hot removed we'll cancel all the delayed work items via gov_cancel_work(). Sometimes the delayed work function determines that it should adjust the delay for all other CPUs that the policy is managing. If this scenario occurs, the canceling CPU will cancel its own work