On Thu, Jan 11, 2018 at 05:16:51PM -0800, Andy Lutomirski wrote:
This tests that the vsyscall entries do what they're expected to do. It also confirms that attempts to read the vsyscall page behave as expected.
If changes are made to the vsyscall code or its memory map handling, running this test in all three of vsyscall=none, vsyscall=emulate, and vsyscall=native are helpful.
(Because it's easy, this also compares the vsyscall results to their vDSO equivalents.)
Cc: stable@vger.kernel.org Signed-off-by: Andy Lutomirski luto@kernel.org
Tested-by: Greg Kroah-Hartman gregkh@linuxfoundation.org Reviewed-by: Greg Kroah-Hartman gregkh@linuxfoundation.org
Note to KAISER backporters: please test this under all three vsyscall modes. Also, in the emulate and native modes, make sure that test_vsyscall_64 agrees with the command line or config option as to which mode you're in. It's quite easy to mess up the kernel such that native mode accidentally emulates or vice versa.
Greg, etc: please backport this to all your Meltdown-patched kernels. It'll help make sure the patches didn't regress vsyscalls.
I will gladly do so, thanks so much for this test.
greg k-h