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

Groups > linux.kernel > #1741247 > unrolled thread

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

Started byIngo Molnar <mingo@kernel.org>
First post2017-09-28 10:00 +0200
Last post2017-09-28 14:00 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

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

FromIngo Molnar <mingo@kernel.org>
Date2017-09-28 10:00 +0200
SubjectRe: [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault
Message-ID<uuBTK-6bp-27@gated-at.bofh.it>
* 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.

Thanks,

	Ingo

[toc] | [next] | [standalone]

#1741269

FromPeter Zijlstra <peterz@infradead.org>
Date2017-09-28 10:20 +0200
Message-ID<uuCd4-6xg-21@gated-at.bofh.it>
In reply to#1741247
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.

[toc] | [prev] | [next] | [standalone]

#1741300

FromIngo Molnar <mingo@kernel.org>
Date2017-09-28 10:50 +0200
Message-ID<uuCG6-6IC-17@gated-at.bofh.it>
In reply to#1741269
* 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

[toc] | [prev] | [next] | [standalone]

#1741469

FromPeter Zijlstra <peterz@infradead.org>
Date2017-09-28 14:00 +0200
Message-ID<uuFDX-8w4-5@gated-at.bofh.it>
In reply to#1741300
On Thu, Sep 28, 2017 at 10:49:41AM +0200, Ingo Molnar wrote:
> > 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.

Ah, I recently had a case where this old GCC-4.4 crashed on 'obviously'
broken code while newer GCC's somehow made it 'work'.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web