linux-kernel - Re: [RFC] selftests/x86: Add test

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALCETrVSab=Xb4gOwfsttOrB-7RpkX0u45Y2Pk0f_8=HTr2Y5g@mail.gmail.com>
Date:   Tue, 9 Jan 2018 13:27:18 -0800
From:   Andy Lutomirski <luto@...nel.org>
To:     Shuah Khan <shuahkhan@...il.com>
Cc:     Andy Lutomirski <luto@...nel.org>, X86 ML <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 Tue, Jan 9, 2018 at 1:25 PM, Shuah Khan <shuahkhan@...il.com> wrote:
> 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.
>

Ok.