linux-kernel - Re: [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 4 Jul 2018 09:23:32 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     kernel test robot <xiaolong.ye@...el.com>
Cc:     Andrew Lutomirski <luto@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        Borislav Petkov <bp@...en8.de>,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        LKP <lkp@...org>
Subject: Re: [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso_32.fail

On Tue, Jul 3, 2018 at 11:58 PM kernel test robot <xiaolong.ye@...el.com> wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 8bb2610bc4967f19672444a7b0407367f1540028 ("x86/entry/64/compat: Preserve r8-r11 in int $0x80")
> [...]
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):

So that commit is expected to fix things, but it also *enabled* the
selftests to warn about the change.

Did you run the new selftest on an old kernel?

It looks that way, because you talk about running the selftests for
commit 8bb2610bc496 (which is 4.17-rc2+), but the dmesg you include is
some ancient version"

    Linux version 4.12.0-10998-g6974f0c

Hmm. Some of those self-tests are very much expected to break on old kernels.

                  Linus