Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2818805ybi; Mon, 17 Jun 2019 10:55:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqws1YCWzVcWh9jo9icQBX1rsXKrZu89qaB++H5RaxFG754nprXgp4wPycVYWkq9M+kU4JGj X-Received: by 2002:a17:90a:950d:: with SMTP id t13mr27001712pjo.81.1560793834326; Mon, 17 Jun 2019 10:50:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560793834; cv=none; d=google.com; s=arc-20160816; b=VftdLyGlXMqpG4JX+lCxV0ZTc9BJnOFfsMtklZ30ATyDWrH3rhvpMrZbc3UMFSVBeB IAoSGNAyi44U9OV/6UnVxV32ZJLFC37SJgQsiq1rcgdkbE3PbMSRZ25qGvhw0F3R5tCS gYfYk5GXVl11IebyZUmlLya49UMvpTtGUBR6pqT4tHlKum3mqDEAgBpCEsYeEx7yaC/l V7H87ulvLtKzgXUmvwhbmc+7NLIun5R59hz+YylblxVHxr0TzRK3hpws6eIkONLLopPd 7FMngbBd35lZJhh5/XwQzDCu/29gJTwWc91z0URhte+1d7JkKzp3upxon7ISI2rUukKM DXnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=mTIMaymR2g7ReedoWbXicVhALRP9n80T++Kcv0+9jtg=; b=Oa1C3nJHw7Pkp/0q+SF1xwpm19mj4TOxTll9ShvkxZZQmVwbgr2zgcQSasX9giQyt3 W2JjiORwAQ/1VsNzAH0eVB2awhDk3+9Ki5OsK8YAVlAjvJqLf7+T+sEzWJLOVAvREln7 +qoq7yi38CEcCDqT0YY/U4JIFiDKkJ8cce6zSsGRknGiR0qcHHtgFP0WUPUqcHFqptQ7 bbq8S9pQ1okkyCWPgjqkOZMTqMrMCgo7NC0oghpV+OHp+fFWlw4OGElsor+cBmCnTXqb sbjiXqOWBWYPl018slcRB2XEFbYxmPsJKOlbm7TSXRRh1fy/CEbdZ8Wgx6ucmpoioXiJ EUoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=google header.b="e0tz/APC"; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x123si11041954pfx.157.2019.06.17.10.50.18; Mon, 17 Jun 2019 10:50:34 -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; dkim=pass header.i=@linux-foundation.org header.s=google header.b="e0tz/APC"; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728561AbfFQRuG (ORCPT + 99 others); Mon, 17 Jun 2019 13:50:06 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:36889 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726047AbfFQRuG (ORCPT ); Mon, 17 Jun 2019 13:50:06 -0400 Received: by mail-lf1-f68.google.com with SMTP id d11so7176663lfb.4 for ; Mon, 17 Jun 2019 10:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mTIMaymR2g7ReedoWbXicVhALRP9n80T++Kcv0+9jtg=; b=e0tz/APC5r77SqUGRyfs/Mwa7FuxmPdocJvVwqMgopem89HfOL1bhcEpLKWmjogU8K 7tnCaXIJLhABAdqAJmR5Xrk33u93+x+oVv8LofRf9OgNyy1lfVfpWErV7PeDRcYYQW6c 63h5TyhdbeMvuJ21173JUk65/NyRsTxCQcS+Q= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mTIMaymR2g7ReedoWbXicVhALRP9n80T++Kcv0+9jtg=; b=kuS/uqK2mJzFcBhCBsOCXmTgZHdRecW0TlnXuRfyP1y7HVb0nUm7FftTLD879Q6WvZ AcEz33jXppt/oA2S+jlBC3WfN68E5piUjc/CGjvZdjoAG09bm6UkyoozddtG37iN5GYI +FeG6LqFQI+FNaDDEdHSGZj/fBe5d1trdz7duCr7GpudTHXzrsaURS60l3pBkBQ1v3OP b1SKy4+8ERFwadgHQjZMJ02PdgLoqmzFZaHrqxQ6i4HQ/golawC7P48WtDkCtUBJwOK2 4+8H/Rj03zPAkHH818yfKOnVPGihFxrewOH5ebLvsQUuJTx55aNRylLK3tlbLSjZ/XWI QtCw== X-Gm-Message-State: APjAAAX1g7xnSNe+wq7wwnisNE63whRY/eDzz8Ri5B797mtXqCp55+8h bWZX0d4yjFloHcfLICQQO2hMtfClEC4= X-Received: by 2002:a19:9156:: with SMTP id y22mr10814434lfj.43.1560793802856; Mon, 17 Jun 2019 10:50:02 -0700 (PDT) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com. [209.85.208.180]) by smtp.gmail.com with ESMTPSA id h84sm2194156ljf.42.2019.06.17.10.50.01 for (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jun 2019 10:50:02 -0700 (PDT) Received: by mail-lj1-f180.google.com with SMTP id i21so10183125ljj.3 for ; Mon, 17 Jun 2019 10:50:01 -0700 (PDT) X-Received: by 2002:a2e:9bc6:: with SMTP id w6mr17389201ljj.156.1560793800661; Mon, 17 Jun 2019 10:50:00 -0700 (PDT) MIME-Version: 1.0 References: <20190319165123.3967889-1-arnd@arndb.de> <87tvd2j9ye.fsf@oldenburg2.str.redhat.com> <871s05fd8o.fsf@oldenburg2.str.redhat.com> <87sgs8igfj.fsf@oldenburg2.str.redhat.com> In-Reply-To: <87sgs8igfj.fsf@oldenburg2.str.redhat.com> From: Linus Torvalds Date: Mon, 17 Jun 2019 10:49:44 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] uapi: avoid namespace conflict in linux/posix_types.h To: Florian Weimer Cc: Joseph Myers , Arnd Bergmann , Linux API , linux-arch , Netdev , Laura Abbott , Paul Burton , Deepa Dinamani , Linux List Kernel Mailing Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 17, 2019 at 4:45 AM Florian Weimer wrote: > > I wanted to introduce a new header, , and include > it where the definition of __kernel_long_t is needed, something like > this (incomplete, untested): So this doesn't look interesting to me: __kernel_long_t is neither interesting as a type anyway (it's just a way for user space to override "long"), nor is it a namespace violation. So honestly, user space could do whatever it wants for __kernel_long_t anyway. The thing that I think we should try to fix is just the "val[]" thing, ie > A different approach would rename to something more > basic, exclude the two structs, and move all internal #includes which do > need the structs to the new header. In fact, I wouldn't even rename at all, I'd just make sure it's namespace-clean. I _think_ the only thing causing problems is '__kernel_fsid_t' due to that "val[]" thing, so just remove ity entirely, and add it to instead. And yeah, then we'd need to maybe make sure that the (couple) of __kernel_fsid_t users properly include that statfs.h file. Hmm? Linus