Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp526533ybi; Fri, 7 Jun 2019 12:03:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqwca06ihflsYEnM3mzuVWTUm2UJCuTd6ULofYM053pvuo/vjC+Q1M+WYPmDhT8uy7mS6H7H X-Received: by 2002:a17:90a:7343:: with SMTP id j3mr7145513pjs.84.1559934188717; Fri, 07 Jun 2019 12:03:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559934188; cv=none; d=google.com; s=arc-20160816; b=gTRJUlF/92R0GEXbMtowWl1AXFt8+hWGcyhXoJX8xaPuhJtXp48ZZdVYkDzCaG3/Hz 9aEu0un1YEJcLQYmV6t6bdHN4XkEz2+fijmF6zFy1ijarCjRAq7cXlEMXvnH0yjvGJ2y YqHwc74TdDN+gEwwqOfgJa7ePPnwpaPrQAlQK0KZkLP5ac0jB5PzCsFf38JfmTbisada aelgJYmHmypxN+fVojtduSu3dubZ4GcmKEgiAfyodt2D9fZ4PjaipIXwB/1hTlZrFZmn Z/TTYT/QSc2TTamxUTKYI4Yt0fJ3zOYQye/AQec55lQ2egbfIAUcfIZV7xTJBt9P4NSI U1AA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from; bh=IbMRNIFQrX5XaPpT/9vmnOJZLV5FrbrbaT3C+jRs8cQ=; b=CYMa889LVR7+tVurgLa1NaSqBwgdEd/LuHxZ+8Vhw6ll6f1Yr8Dks/btaiw+KgSArK zspkY3J4vtY9dHuXDBR9Acq6TA7Q8yjTHiUAeMtmvONlZTBgo0G/3WTEe0f/aACcngEh 86aVYW7j350CEm9ZYLga7sO5Ti09VbuMu+HvclswnQt8Vlv09B0BqJfYiRnYcv4GWBoT lQqqEDaXWZpRtsQbd1AfmwAXrgaEnDxab9Y59fNk2McBK9YKcUlLZOCrxq0hO0BAKVsR 0SMWipAyaoBH9YwSn9sM6FCNhmLZY54XrOIB54Ol4AOBKs4fjUZGNZkkR1GfPM3QV04O h2Mg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n26si2869054pgv.264.2019.06.07.12.02.52; Fri, 07 Jun 2019 12:03:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731911AbfFGSnP (ORCPT + 99 others); Fri, 7 Jun 2019 14:43:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48226 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729449AbfFGSnP (ORCPT ); Fri, 7 Jun 2019 14:43:15 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 19B81308FC4E; Fri, 7 Jun 2019 18:43:15 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-116-64.ams2.redhat.com [10.36.116.64]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D2AD27856D; Fri, 7 Jun 2019 18:43:05 +0000 (UTC) From: Florian Weimer To: Linus Torvalds Cc: Joseph Myers , Arnd Bergmann , Linux API , linux-arch , Netdev , Laura Abbott , Paul Burton , Deepa Dinamani , Linux List Kernel Mailing Subject: Re: [PATCH] uapi: avoid namespace conflict in linux/posix_types.h References: <20190319165123.3967889-1-arnd@arndb.de> <87tvd2j9ye.fsf@oldenburg2.str.redhat.com> Date: Fri, 07 Jun 2019 20:43:03 +0200 In-Reply-To: (Linus Torvalds's message of "Fri, 7 Jun 2019 11:27:57 -0700") Message-ID: <871s05fd8o.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Fri, 07 Jun 2019 18:43:15 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Linus Torvalds: > If we're changing kernel header files, it's easy enough to change the > kernel users. I'd be more worried about user space that *uses* that > thing, and currently accesses 'val[]' by name. > > So the patch looks a bit odd to me. How are people supposed to use > fsid_t if they can't look at it? The problem is that the header was previously not used pervasively in userspace headers. See commit a623a7a1a5670c25a16881f5078072d272d96b71 ("y2038: fix socket.h header inclusion"). Very little code needed it before. On the glibc side, we nowadays deal with this by splitting headers further. (We used to suppress definitions with macros, but that tended to become convoluted.) In this case, moving the definition of __kernel_long_t to its own header, so that include/uapi/asm-generic/socket.h can include that should fix it. > So now that I _do_ see the patch, there's no way I'll apply it. Fair enough. Thanks, Florian