diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2013-07-05 12:09:18 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2013-07-05 17:25:58 +0200 |
commit | 5ec2481b7b47a4005bb446d176e5d0257400c77d (patch) | |
tree | e7ae9e34dc6b1db5149669947b6cd93814f447ec /fs/coda/symlink.c | |
parent | 332962f2c88868ed3cdab466870baaa34dd58612 (diff) |
hrtimers: Move SMP function call to thread context
smp_call_function_* must not be called from softirq context.
But clock_was_set() which calls on_each_cpu() is called from softirq
context to implement a delayed clock_was_set() for the timer interrupt
handler. Though that almost never gets invoked. A recent change in the
resume code uses the softirq based delayed clock_was_set to support
Xens resume mechanism.
linux-next contains a new warning which warns if smp_call_function_*
is called from softirq context which gets triggered by that Xen
change.
Fix this by moving the delayed clock_was_set() call to a work context.
Reported-and-tested-by: Artem Savkov <artem.savkov@gmail.com>
Reported-by: Sasha Levin <sasha.levin@oracle.com>
Cc: David Vrabel <david.vrabel@citrix.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: H. Peter Anvin <hpa@zytor.com>,
Cc: Konrad Wilk <konrad.wilk@oracle.com>
Cc: John Stultz <john.stultz@linaro.org>
Cc: xen-devel@lists.xen.org
Cc: stable@vger.kernel.org
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'fs/coda/symlink.c')
0 files changed, 0 insertions, 0 deletions