Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751338AbdFBHHj (ORCPT ); Fri, 2 Jun 2017 03:07:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:26848 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751187AbdFBHHh (ORCPT ); Fri, 2 Jun 2017 03:07:37 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 4FE7620B14 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 4FE7620B14 Subject: Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions To: "Carlos O'Donell" , Hauke Mehrtens , musl@lists.openwall.com, David Woodhouse , Felix Janda , linux-kernel@vger.kernel.org Cc: "David S. Miller" , linux-api@vger.kernel.org References: <20161111120820.GA435@nyan> <1488977188.4347.134.camel@infradead.org> <459a8faf-4585-5063-3d94-3a1fecfa8289@redhat.com> <21e624b9-7ab1-dcf9-fb1e-c31dd564a283@hauke-m.de> <9f591383-6e4c-c231-1e5b-68e4b8c16d94@redhat.com> From: Florian Weimer Message-ID: <74e5c515-d924-c4d8-69ad-aeb57d1c4ef0@redhat.com> Date: Fri, 2 Jun 2017 09:07:26 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <9f591383-6e4c-c231-1e5b-68e4b8c16d94@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 02 Jun 2017 07:07:31 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 583 Lines: 14 On 04/25/2017 02:29 PM, Carlos O'Donell wrote: > In glibc right now we support including linux or glibc header files first, > and this has always been a requirement from the start. This requirement dictates > that the kernel know which libc it's being used with so it can tailor coordination. “right now we support” is not a support commitment, but more of an aspiration, right? A lot of combinations are broken, especially when kernel headers are included first. Maybe it's time for us to admit defeat and come up with a simpler scheme which actually works. Thanks, Florian