[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180705003910.GD10005@yexl-desktop>
Date: Thu, 5 Jul 2018 08:39:10 +0800
From: Ye Xiaolong <xiaolong.ye@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
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 07/04, Linus Torvalds wrote:
>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
Just double checked the attached dmesg, the version seems correct, did you
check the right one?
[ 0.000000] Linux version 4.17.0-rc2-00006-g8bb2610 (kbuild@...ro) (gcc version 7.3.0 (Debian 7.3.0-16)) #1 SMP Thu Jun 7 15:10:14 CST 2018
Thanks,
Xiaolong
>
>Hmm. Some of those self-tests are very much expected to break on old kernels.
>
> Linus
Powered by blists - more mailing lists