diff options
| author | Thomas Gleixner | 2020-01-14 19:52:38 +0100 |
|---|---|---|
| committer | Thomas Gleixner | 2020-01-17 15:53:50 +0100 |
| commit | 9a6b55ac4a44060bcb782baf002859b2a2c63267 (patch) | |
| tree | 511a3f83b91584cb4a1da35f0cd1837ac647e894 /kernel | |
| parent | de95a991bb72e009f47e0c4bbc90fc5f594588d5 (diff) | |
lib/vdso: Make __arch_update_vdso_data() logic understandable
The function name suggests that this is a boolean checking whether the
architecture asks for an update of the VDSO data, but it works the other
way round. To spare further confusion invert the logic.
Fixes: 44f57d788e7d ("timekeeping: Provide a generic update_vsyscall() implementation")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20200114185946.656652824@linutronix.de
Diffstat (limited to 'kernel')
| -rw-r--r-- | kernel/time/vsyscall.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/time/vsyscall.c b/kernel/time/vsyscall.c index 5ee0f7709410..f0aab6182824 100644 --- a/kernel/time/vsyscall.c +++ b/kernel/time/vsyscall.c @@ -84,7 +84,7 @@ void update_vsyscall(struct timekeeper *tk) struct vdso_timestamp *vdso_ts; u64 nsec; - if (__arch_update_vdso_data()) { + if (!__arch_update_vdso_data()) { /* * Some architectures might want to skip the update of the * data page. |