From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751776AbdI1H7M (ORCPT ); Thu, 28 Sep 2017 03:59:12 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:48720 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750981AbdI1H7L (ORCPT ); Thu, 28 Sep 2017 03:59:11 -0400 X-Google-Smtp-Source: AOwi7QCkqESgKa2G3YASku1mn87GXGdtmbf+CMKzz5MLkVC4yAWy7YO+W9CNeORsXUwfQnzX4D9HBw== Date: Thu, 28 Sep 2017 09:59:07 +0200 From: Ingo Molnar To: kernel test robot Cc: Josh Poimboeuf , Andrey Ryabinin , Matthias Kaehlcke , Alexander Potapenko , Andy Lutomirski , Arnd Bergmann , Dmitriy Vyukov , Linus Torvalds , Miguel Bernal Marin , Peter Zijlstra , Thomas Gleixner , LKML , lkp@01.org Subject: Re: [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault Message-ID: <20170928075907.bpxlop6bq4bn54sk@gmail.com> References: <20170928074758.GS17200@yexl-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170928074758.GS17200@yexl-desktop> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * kernel test robot 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1126962325572135946==" MIME-Version: 1.0 From: Ingo Molnar To: lkp@lists.01.org Subject: Re: [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault Date: Thu, 28 Sep 2017 09:59:07 +0200 Message-ID: <20170928075907.bpxlop6bq4bn54sk@gmail.com> In-Reply-To: <20170928074758.GS17200@yexl-desktop> List-Id: --===============1126962325572135946== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable * kernel test robot wrote: > = > FYI, we noticed the following commit: > = > commit: f5caf621ee357279e759c0911daf6d55c7d36f03 ("x86/asm: Fix inline as= m 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=3D'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 year= s ago. Thanks, Ingo --===============1126962325572135946==--