On Sun, 2018-03-18 at 11:27 +0100, Greg Kroah-Hartman wrote: > On Sat, Mar 17, 2018 at 03:48:24PM +0530, Naresh Kamboju wrote: [...] > > Results from Linaro’s test farm. > > No regressions on arm64, arm, qemu_x86_64 and x86_64. > > > > NOTE: > > CONFIG_LEGACY_VSYSCALL_EMULATE=y is enabled from config as default. > > Enabled vsyscall=native and vsyscall=none from kernel command line for > > testing > > selftests/x86/test_vsyscall test case on x86_64 and qemu_x86_64. > > > > test_vdso_64 failed on x86_64 device when vsyscall=none is enabled. > > We will investigate this new test failure. > > I think vsyscall=none just went away :)
No, vsyscall=native went away upstream. vsyscall=none should still work everywhere. However, test_vdso_64 isn't able to detect what the current configuration is and it will crash with vsyscall=none (or the equivalent default in kconfig). Ben. -- Ben Hutchings Software Developer, Codethink Ltd.
