Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751245AbdFAUoV (ORCPT ); Thu, 1 Jun 2017 16:44:21 -0400 Received: from b.ns.miles-group.at ([95.130.255.144]:44723 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751128AbdFAUoU (ORCPT ); Thu, 1 Jun 2017 16:44:20 -0400 Subject: Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a To: Florian Fainelli , linux-kernel@vger.kernel.org, Thomas Meyer 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> 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)" From: Richard Weinberger Message-ID: <07b61d6a-33af-be0a-b57c-843196d0d151@nod.at> Date: Thu, 1 Jun 2017 22:44:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1085 Lines: 25 Am 01.06.2017 um 22:40 schrieb Florian Fainelli: >>> Sure, but that seems orthogonal? In the absence of an answer from Eli, >>> either you could take my patch or just send reverts of Eli's two >>> commits, whichever you prefer. >> >> Or you and Thomas could investigate. :-) > > Honestly, I don't know what do you want me to investigate, my host > machine is old (2.6.32) and does not support PTRACE_GETREGSET or > friends, nor does it have _xstate, so with that, we either don't use > those period, which would be a revert, or we just conditionally build > support for that (my patch) and everyone is happy. This is exactly why we have this mess right now. Everybody is just focusing on his own stuff. > I don't know what the issue Thomas is having (he is now CC'd) and I > still don't understand why you insist on conflating the symbol clash > while statically linking with support for newer x86 FPU stuff... The said commits introduced issues, you face some, Thomas is facing some. I want them to get fixed or at least understood before we apply new patches. Thanks, //richard