Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp5680627iob; Tue, 10 May 2022 00:45:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwxpLD6ORnKogQmcrtdJ7x0lDLoctFqWP3ruhBA2IBQOIKL35hoBMHmRlOE5lMwj4Y8uk2P X-Received: by 2002:a05:6402:1f0b:b0:427:b390:2020 with SMTP id b11-20020a0564021f0b00b00427b3902020mr21614673edb.70.1652168750186; Tue, 10 May 2022 00:45:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652168750; cv=none; d=google.com; s=arc-20160816; b=F7iJzu2Eavudu68ydCkfN9/iL0n5TeoBizSzCz1u6lObYhXILrf0AyEFJTPb60SkQX 8ZVQAmUKyJJ5npETgneMwOZRVL2DkYugnl+ZQ/f5M6BZ0nVXoyPZNP9LhZWGwIImHSg/ Me4ExelbfoATyreWQ1usrU6+Sj9rJecUHMf/IXyyjRXjzY4IX4J3v0JTy+vZ4H0TqM7l 0Qwk1bWlyR+tb239W6KsIhvcRAx4qBpbGU3SyDuZv9qUe89MneTAA2OMP5taiThtI8IO WnwzofcXZpWNazzQWiRYvS5v5aQ9Tl7RXJlqvo53DcR245zor2oFwFe+z/gkW72rBKU0 Z/RA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature:dkim-signature; bh=Wf4+GirlHr8odLVWkz1C4aI3GGmAypu/lVakO44m7ok=; b=ZmXKRb1TV/pitkIdHaAk2yoZu6G6pXHhKNmF8YK6ivXu9X2BwSK1OtOII2AaX9/ccl BRJXppUI2LTjEwQM3MYaiKIachCzygOHJUmMms3oCJTcW8ktrTr66ul4YefsaeVCd7ET V0sTckv0mQHAfTFbf1QTmHzKIMeKt+0p/oNUDCs2hYqzb+I93U3RNLKLZTvYNklkqo5o nzo6k6aO+rkYPRZfGQx4peuUOs1GzOmnzgXReFSGkgH9HbzJqhR3dYNJU87GryYz4WJq aIYW+/jFMqPz5gO4RJPmo5klO8W6FgkPK3bLF0kvV0qmcpKOCZBNDWPqTIaTard9bgFT UQRg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@themaw.net header.s=fm3 header.b="Kd6w/Ky9"; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=z4cDqglD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s6-20020a056402520600b00425cb569c52si17622129edd.281.2022.05.10.00.45.27; Tue, 10 May 2022 00:45:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@themaw.net header.s=fm3 header.b="Kd6w/Ky9"; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=z4cDqglD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235631AbiEJDmV (ORCPT + 99 others); Mon, 9 May 2022 23:42:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38670 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235709AbiEJDkh (ORCPT ); Mon, 9 May 2022 23:40:37 -0400 Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B2FFE2016C7; Mon, 9 May 2022 20:34:54 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 5917D3200976; Mon, 9 May 2022 23:34:52 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 09 May 2022 23:34:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=themaw.net; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1652153691; x= 1652240091; bh=Wf4+GirlHr8odLVWkz1C4aI3GGmAypu/lVakO44m7ok=; b=K d6w/Ky9g1ONou+rs8boNzVnFBHtYNFA1WbynVGD24JKcYKLWqLU6/jX/6JNP7rak PHLtOTz43QnIoy5mF8GRfgKHt+ESvwLJW13bIwbI7ikNVBPAlj4zg6JAzwUnNFPN jGn5u15qQuWJM4OPcfg2QGSuBdFKbuBk4yAelyVa6gcBpJM3twzbBseiBTAy4Dcs /kfW5db8YGVUfH/Li6584SZtEKKusdFuj0ZHDQTyXmOLcxj3w8qshaXGb9E9LdrC RCqb2sorM7VVhmpc4aSR1kGSolhW1dU3MoAm4IL5wnrVXTA63daH729Y3LfVseIo FRbmIkOl+MldRigeH5ybQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1652153691; x=1652240091; bh=Wf4+GirlHr8od LVWkz1C4aI3GGmAypu/lVakO44m7ok=; b=z4cDqglDdqc/osHgQ2M74yL21q/ld on9l+ORXm2aR824S7xOaod5uSPAVxA5Aejyxb4Sf2cvRQuzghCC/TdyWxCFeeewX /A0f22gQbVUlyu2/fEFWAGb6aXHaXu9M+uPFDkXsn4UBgFWNjYpuaeYjuQUO/hpx HR217Tpo2MtH4wzCJMYaPWK5Ku8OtXiYDmq/nW7f5UMwFYwxZ9y4X+a9kxEczDHi KqWv5mS8iuL9A6ieNtYMLCqQYR9UVkMM0mg5DMWL/ocJ11sni2H/RUXdVBJCUtD6 J7UZXsSTYbm7oLgZlQIVY39m0lyXOScdGjABK0D2Nk7rEpblfpf3/BI3w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgedtgdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkuffhvfevffgjfhgtfggggfesthejredttderjeenucfhrhhomhepkfgrnhcu mfgvnhhtuceorhgrvhgvnhesthhhvghmrgifrdhnvghtqeenucggtffrrghtthgvrhhnpe dviefhveeifeevfedutdffkeeigedukeehvefgteeileeitdehgffggfffveejteenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehrrghvvghnse hthhgvmhgrfidrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 9 May 2022 23:34:45 -0400 (EDT) Message-ID: <4a712f3618835ac9ba0db8d26630f8edf209a193.camel@themaw.net> Subject: Re: [RFC PATCH] getting misc stats/attributes via xattr API From: Ian Kent To: Vivek Goyal , Christian Brauner Cc: Amir Goldstein , Miklos Szeredi , linux-fsdevel , Dave Chinner , Theodore Ts'o , Karel Zak , Greg KH , linux-kernel , Linux API , linux-man , LSM , David Howells , Linus Torvalds , Al Viro , Christian Brauner , James Bottomley Date: Tue, 10 May 2022 11:34:39 +0800 In-Reply-To: References: <20220509124815.vb7d2xj5idhb2wq6@wittgenstein> <20220509150856.cfsxn5t2tvev2njx@wittgenstein> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-1.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2022-05-09 at 17:42 -0400, Vivek Goyal wrote: > On Mon, May 09, 2022 at 05:08:56PM +0200, Christian Brauner wrote: > > [..] > > Having "xattr" in the system call name is just confusing. These are > > fundamentally not "real" xattrs and we shouldn't mix semantics. > > There > > should be a clear distinction between traditional xattrs and this > > vfs > > and potentially fs information providing interface. > > > > Just thinking about what the manpage would look like. We would need > > to > > add a paragraph to xattr(7) explaining that in addition to the > > system.*, > > security.*, user.* and other namespaces we now also have a set of > > namespaces that function as ways to get information about mounts or > > other things instead of information attached to specific inodes. > > > > That's super random imho. If I were to be presented with this > > manpage > > I'd wonder if someone was too lazy to add a proper new system call > > with > > it's own semantics for this and just stuffed it into an existing > > API > > because it provided matching system call arguments. We can add a > > new > > system call. It's not that we're running out of them. > > FWIW, I also felt that using xattr API to get some sort of mount info > felt > very non-intutive. Yeah, people looking for this function simply wouldn't know to look here ... Ian