All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso_32.fail
Date: Thu, 05 Jul 2018 08:39:10 +0800	[thread overview]
Message-ID: <20180705003910.GD10005@yexl-desktop> (raw)
In-Reply-To: <CA+55aFwSD8T1dusD_Q14MhAxQcYG===ZTdS+CXuT-odj88xWkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On 07/04, Linus Torvalds wrote:
>On Tue, Jul 3, 2018 at 11:58 PM kernel test robot <xiaolong.ye@intel.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(a)cairo) (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

WARNING: multiple messages have this Message-ID (diff)
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	LKP <lkp@01.org>
Subject: Re: [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso_32.fail
Date: Thu, 5 Jul 2018 08:39:10 +0800	[thread overview]
Message-ID: <20180705003910.GD10005@yexl-desktop> (raw)
In-Reply-To: <CA+55aFwSD8T1dusD_Q14MhAxQcYG===ZTdS+CXuT-odj88xWkA@mail.gmail.com>

On 07/04, Linus Torvalds wrote:
>On Tue, Jul 3, 2018 at 11:58 PM kernel test robot <xiaolong.ye@intel.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@cairo) (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

  parent reply	other threads:[~2018-07-05  0:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  6:54 [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso_32.fail kernel test robot
2018-07-04  6:54 ` kernel test robot
2018-07-04 16:23 ` Linus Torvalds
2018-07-04 16:23   ` Linus Torvalds
2018-07-04 18:30   ` Andy Lutomirski
2018-07-04 21:14     ` Linus Torvalds
2018-07-04 21:14       ` Linus Torvalds
2018-07-05  0:39   ` Ye Xiaolong [this message]
2018-07-05  0:39     ` Ye Xiaolong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180705003910.GD10005@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=lkp@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.