aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2007-07-03 20:05:20 +0200
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-03 13:54:27 -0700
commit746976a301ac9c9aa10d7d42454f8d6cdad8ff2b (patch)
tree8173b3b64542b81d94dbb4614b42db66fffbc4d2 /Documentation
parent872aad45d6174570dd2e1defc3efee50f2cfcc72 (diff)
downloadkernel_samsung_crespo-746976a301ac9c9aa10d7d42454f8d6cdad8ff2b.zip
kernel_samsung_crespo-746976a301ac9c9aa10d7d42454f8d6cdad8ff2b.tar.gz
kernel_samsung_crespo-746976a301ac9c9aa10d7d42454f8d6cdad8ff2b.tar.bz2
NTP: remove clock_was_set() call to prevent deadlock
The clock_was_set() call in seconds_overflow() which happens only when leap seconds are inserted / deleted is wrong in two aspects: 1. it results in a call to on_each_cpu() with interrupts disabled 2. it is potential deadlock source vs. call_lock in smp_call_function() The only possible side effect of the removal might be, that an absolute CLOCK_REALTIME timer fires 1 second too late, in the rare case of leap second deletion and an absolute CLOCK_REALTIME timer which expires in the affected time frame. It will never fire too early. This was probably observed by the reporter of a June 30th -> July 1st hang: http://lkml.org/lkml/2007/7/3/103 A similar problem was observed by Dave Jones, who provided a screen shot with a lockdep back trace, which allowed to analyse the problem. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions