Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751298AbdFBNSb (ORCPT ); Fri, 2 Jun 2017 09:18:31 -0400 Received: from www17.your-server.de ([213.133.104.17]:47328 "EHLO www17.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbdFBNSa (ORCPT ); Fri, 2 Jun 2017 09:18:30 -0400 Message-ID: <1496409482.10119.1.camel@m3y3r.de> Subject: Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a From: Thomas Meyer To: Richard Weinberger , Florian Fainelli , linux-kernel@vger.kernel.org Cc: Jeff Dike , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , "open list:USER-MODE LINUX (UML)" , "open list:USER-MODE LINUX (UML)" Date: Fri, 02 Jun 2017 15:18:02 +0200 In-Reply-To: References: <20170524003232.14319-1-f.fainelli@gmail.com> <9f58b41d-ebe4-62a6-1aa4-e9222372ce86@gmail.com> <408132c9-6d55-7cba-e09a-f532d7fb9c6f@gmail.com> <9617f203-cee2-96cf-aa76-8f42b1a4a9f6@nod.at> <2c362d49-9907-7a66-67ef-e196dddea32a@gmail.com> <85f8b8c0-cf0e-3c67-c237-be4b045c617b@nod.at> <07b61d6a-33af-be0a-b57c-843196d0d151@nod.at> <8dd50867-312d-8af9-0993-4b5d5c181a58@gmail.com> <1496352322.9072.1.camel@m3y3r.de> <3672f56d-da81-1114-f06a-ac99d3680661@gmail.com> <1496390649.2047.2.camel@m3y3r.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: thomas@m3y3r.de Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2119 Lines: 54 Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > > [ 0.000000] ------------[ cut here ]------------ > > [ 0.000000] WARNING: CPU: 0 PID: 0 at > > arch/x86/kernel/fpu/xstate.c:595 > > fpu__init_system_xstate+0x4d0/0x877 > > [ 0.000000] XSAVE consistency problem, dumping leaves > > [ 0.000000] Modules linked in: > > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.10.15- > > 200.fc25.x86_64 #1 > > [ 0.000000] Call Trace: > > [ 0.000000] dump_stack+0x63/0x86 > > [ 0.000000] __warn+0xcb/0xf0 > > [ 0.000000] warn_slowpath_fmt+0x5f/0x80 > > [ 0.000000] ? xfeature_size+0x5a/0x78 > > [ 0.000000] fpu__init_system_xstate+0x4d0/0x877 > > [ 0.000000] ? msr_clear_bit+0x3a/0xa0 > > [ 0.000000] ? 0xffffffffa3000000 > > [ 0.000000] fpu__init_system+0x194/0x1be > > [ 0.000000] early_cpu_init+0xf7/0xf9 > > [ 0.000000] setup_arch+0xba/0xcf0 > > [ 0.000000] ? printk+0x57/0x73 > > [ 0.000000] ? early_idt_handler_array+0x120/0x120 > > [ 0.000000] start_kernel+0xb2/0x48a > > [ 0.000000] ? early_idt_handler_array+0x120/0x120 > > [ 0.000000] x86_64_start_reservations+0x24/0x26 > > [ 0.000000] x86_64_start_kernel+0x14d/0x170 > > [ 0.000000] start_cpu+0x14/0x14 > > [ 0.000000] ---[ end trace d5213d72358dda94 ]--- > > [ 0.000000] CPUID[0d, 00]: eax=00000007 ebx=00000440 > > ecx=00000440 edx=00000000 > > Does this also happen with a mainline kernel? Yes, same error on current master on bare metal: [ 5.300000] Key type encrypted registered [ 5.300000] This architecture does not have kernel memory protection. [ 5.300000] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b * master 3b1e342be265 Merge tag 'nfsd-4.12-1' of git://linux-nfs.org/~bfields/linux > Also on KVM or bare metal? > Not that UML fails because of this and we're hunting a ghost... > > Thanks, > //richard >