[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKocOOOqoh0RcsxSK21rXqhOUfz-h6A542fN4frSMW6c+EE2Vg@mail.gmail.com>
Date: Tue, 9 Jan 2018 14:25:00 -0700
From: Shuah Khan <shuahkhan@...il.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: x86@...nel.org, LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [RFC] selftests/x86: Add test_vsyscall
On Thu, Jan 4, 2018 at 10:38 PM, Andy Lutomirski <luto@...nel.org> 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.)
>
> Signed-off-by: Andy Lutomirski <luto@...nel.org>
> ---
>
Hi Andy,
I am not cc'ed on this patch. Doesn't look like the patch is sent to everybody
get_maintainers lists for the set of files that are changed in this patch.
Please make sure to include everybody on your future kselftest patches.
thanks,
-- Shuah
Powered by blists - more mailing lists