diff options
| author |   John Stultz <john.stultz@linaro.org> | 2014-03-27 16:30:49 -0700 |
|---|---|---|
| committer |   Ingo Molnar <mingo@kernel.org> | 2014-03-28 08:07:07 +0100 |
| commit | cab5e127eef040399902caa8e1510795583fa03a (patch) | |
| tree | 9e9a5713d4d58ffafea24354537e8207bd013c7e /net/unix/sysctl_net_unix.c | |
| parent | vfs: Allocate anon_inode_inode in anon_inode_init() (diff) | |
| download | wireguard-linux-cab5e127eef040399902caa8e1510795583fa03a.tar.xz wireguard-linux-cab5e127eef040399902caa8e1510795583fa03a.zip | |
time: Revert to calling clock_was_set_delayed() while in irq context
In commit 47a1b796306356f35 ("tick/timekeeping: Call
update_wall_time outside the jiffies lock"), we moved to calling
clock_was_set() due to the fact that we were no longer holding
the timekeeping or jiffies lock.
However, there is still the problem that clock_was_set()
triggers an IPI, which cannot be done from the timer's hard irq
context, and will generate WARN_ON warnings.
Apparently in my earlier testing, I'm guessing I didn't bump the
dmesg log level, so I somehow missed the WARN_ONs.
Thus we need to revert back to calling clock_was_set_delayed().
Signed-off-by: John Stultz <john.stultz@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/1395963049-11923-1-git-send-email-john.stultz@linaro.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions