summaryrefslogtreecommitdiff
path: root/kernel/time
diff options
context:
space:
mode:
authorHugh Dickins <hughd@google.com>2018-02-13 16:45:20 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-02-17 13:21:12 +0100
commit83946c33b9b99b5bc6157cfbf3970265f006c2bf (patch)
treec4061e8d3558b0fbbd93e5d6186f2f1fbd4da8c5 /kernel/time
parent297c7cc4b5651b174a62925b6c961085f04979fd (diff)
kaiser: fix compile error without vsyscall
Tobias noticed a compile error on 4.4.115, and it's the same on 4.9.80: arch/x86/mm/kaiser.c: In function ‘kaiser_init’: arch/x86/mm/kaiser.c:348:8: error: ‘vsyscall_pgprot’ undeclared (first use in this function) It seems like his combination of kernel options doesn't work for KAISER. X86_VSYSCALL_EMULATION is not set on his system, while LEGACY_VSYSCALL is set to NONE (LEGACY_VSYSCALL_NONE=y). He managed to get things compiling again, by moving the 'extern unsigned long vsyscall_pgprot' outside of the preprocessor statement. This works because the optimizer removes that code (vsyscall_enabled() is always false) - and that's how it was done in some older backports. Reported-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de> Signed-off-by: Hugh Dickins <hughd@google.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/time')
0 files changed, 0 insertions, 0 deletions