Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1741300

Re: [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault

From Ingo Molnar <mingo@kernel.org>
Newsgroups linux.kernel
Subject Re: [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault
Date 2017-09-28 10:50 +0200
Message-ID <uuCG6-6IC-17@gated-at.bofh.it> (permalink)
References <uuBTJ-6bp-17@gated-at.bofh.it> <uuBTK-6bp-27@gated-at.bofh.it> <uuCd4-6xg-21@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Thu, Sep 28, 2017 at 09:59:07AM +0200, Ingo Molnar wrote:
> > 
> > * kernel test robot <xiaolong.ye@intel.com> wrote:
> > 
> > > 
> > > FYI, we noticed the following commit:
> > > 
> > > commit: f5caf621ee357279e759c0911daf6d55c7d36f03 ("x86/asm: Fix inline asm call constraints for Clang")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > > 
> > > in testcase: trinity
> > > with following parameters:
> > > 
> > > 	runtime: 300s
> > > 
> > > test-description: Trinity is a linux system call fuzz tester.
> > > test-url: http://codemonkey.org.uk/projects/trinity/
> > > 
> > > 
> > > on test machine: qemu-system-x86_64 -enable-kvm -m 420M
> > > 
> > > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > > 
> > > 
> > > +-----------------------------------------+------------+------------+
> > > |                                         | 0d0970eef3 | f5caf621ee |
> > > +-----------------------------------------+------------+------------+
> > > | boot_successes                          | 9          | 4          |
> > > | boot_failures                           | 0          | 4          |
> > > | PANIC:double_fault                      | 0          | 4          |
> > > | Kernel_panic-not_syncing:Machine_halted | 0          | 4          |
> > > +-----------------------------------------+------------+------------+
> > 
> > I think a key piece of information is that the test is using GCC 4.4:
> > 
> >         export compiler='gcc-4.4'
> > 
> > ... which is pretty old compared to what gets tested typically.
> > 
> > GCC 4.4 was released in 2009 (!), the last minor update of 4.4.7 was 5 years ago.
> 
> Sure, but its still an officially supported GCC version. So either it
> must be made to work, or we must update the minimal GCC version
> requirements for the kernel.

Of course! I just mean I'd not be surprised if this was a GCC bug/quirk
with legacy GCC versions that probably won't be fixed.

Thanks,

	Ingo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [lkp-robot] [x86/asm]  f5caf621ee: PANIC:double_fault Ingo Molnar <mingo@kernel.org> - 2017-09-28 10:00 +0200
  Re: [lkp-robot] [x86/asm]  f5caf621ee: PANIC:double_fault Peter Zijlstra <peterz@infradead.org> - 2017-09-28 10:20 +0200
    Re: [lkp-robot] [x86/asm]  f5caf621ee: PANIC:double_fault Ingo Molnar <mingo@kernel.org> - 2017-09-28 10:50 +0200
      Re: [lkp-robot] [x86/asm]  f5caf621ee: PANIC:double_fault Peter Zijlstra <peterz@infradead.org> - 2017-09-28 14:00 +0200

csiph-web