Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp478302pxa; Wed, 12 Aug 2020 06:56:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzCkXCttUZLi8HlB6GbbMsefvCeNm1xb4jgv3GAAunAEKaVRKUJZIqbFBq/rzcBOr9rhrC5 X-Received: by 2002:a05:6402:b45:: with SMTP id bx5mr22621edb.214.1597240560485; Wed, 12 Aug 2020 06:56:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597240560; cv=none; d=google.com; s=arc-20160816; b=MeEoiaGRzkBev3gX+Kzh2bHmK9NZ6W8dHZYB+NKreohn7jojXtfiv7pHoSvaIvIlbu QX/wsVc83pawo+k35fgLGiD5aYY98gRVdjuca6VB7cMaX7fyOF+ePKh3kwQj1d2rLa1U oK84Nx7drjKjmNkEFYRKbXK2QmN+UmvGfTfRdshaGvrIOsr21mlq5byzy42Si5kSGxGb 6OlDb/Oa55Dvg6v3n/+ECNUxJ73YbsGJ8S0ZEJCUhPL9ibuKSfxsO5+Ns0gx+NUCB850 E+0SCrVhh9mMEslqwg+YQtXx8UmpLM3kfxxh8u8gUuT0sSwdEJYX5lB3K8ox7z4jLp70 rFDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:content-id:mime-version :subject:cc:to:references:in-reply-to:from:organization :dkim-signature; bh=1TkqhIHAzlrLj7I5xdhISZ7mj66OJ1mZ2fQ987mrYKM=; b=jHlIlTrFpwYq24F7+1VV8kbwcuuf823Zi5P4ArRRtC9CmIhigXTNKNSC7wV1TgxBxm 4/mjkHOS4BasqQdKd1z2S+J2+/t84nEBhsvrKySk2//QcmehEaBsxYZKO845SoPQVpFs LYBUyGtY9PS7lo4qBOtYUavkkIi6Cu6Dq0EcMb3Kz+FyRC1e4J7HZ23ePIUHagD8zhDc XMu3o4FCKjyc9p3piYdK4YvQkcPfrjpcPtTk4TPvymzMzPyLZs350EE7YGCK/cWbELTB 5dRixTlThqKpiZeCiQPxPstgY7yghpoczDFQxYQH+tsAWz5vzlOb41MQC6G+P/ui/bCe zQIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="g/LYwh6t"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b24si1185348eje.471.2020.08.12.06.55.36; Wed, 12 Aug 2020 06:56:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="g/LYwh6t"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728025AbgHLNy4 (ORCPT + 99 others); Wed, 12 Aug 2020 09:54:56 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:45288 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726804AbgHLNyz (ORCPT ); Wed, 12 Aug 2020 09:54:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1597240494; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1TkqhIHAzlrLj7I5xdhISZ7mj66OJ1mZ2fQ987mrYKM=; b=g/LYwh6tpsMyYnBcTk4BRCIhn3SxqTIrn/eFVvbrL2/CPbEYu1ke09jO//SbvMzg7Nkcb6 4/engHAlnbjWC/Q0CVAQcAiJpnpxMTWyOzWyG+PBMm+zmsQI2WkgNdGvhQhzK0C0cDKim2 agIEwTGZLe8y+r1nkJeyKwo4GvwRBMc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-222-LT3TPafRN1yp_5xqry4Ptg-1; Wed, 12 Aug 2020 09:54:52 -0400 X-MC-Unique: LT3TPafRN1yp_5xqry4Ptg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7C33291274; Wed, 12 Aug 2020 13:54:50 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-120-127.rdu2.redhat.com [10.10.120.127]) by smtp.corp.redhat.com (Postfix) with ESMTP id A17DF60BF3; Wed, 12 Aug 2020 13:54:47 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <1842689.1596468469@warthog.procyon.org.uk> <1845353.1596469795@warthog.procyon.org.uk> <20200811135419.GA1263716@miu.piliscsaba.redhat.com> To: Linus Torvalds Cc: dhowells@redhat.com, Miklos Szeredi , linux-fsdevel , Al Viro , Karel Zak , Jeff Layton , Miklos Szeredi , Nicolas Dichtel , Christian Brauner , Lennart Poettering , Linux API , Ian Kent , LSM , Linux Kernel Mailing List Subject: Re: file metadata via fs API (was: [GIT PULL] Filesystem Information) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <135550.1597240486.1@warthog.procyon.org.uk> Date: Wed, 12 Aug 2020 14:54:46 +0100 Message-ID: <135551.1597240486@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > IOW, if you do something more along the lines of > > fd = open(""foo/bar", O_PATH); > metadatafd = openat(fd, "metadataname", O_ALT); > > it might be workable. What is it going to walk through? You need to end up with an inode and dentry from somewhere. It sounds like this would have to open up a procfs-like magic filesystem, and walk into it. But how would that actually work? Would you create a new superblock each time you do this, labelled with the starting object (say the dentry for "foo/bar" in this case), and then walk from the root? An alternative, maybe, could be to make a new dentry type, say, and include it in the superblock of the object being queried - and let the filesystems deal with it. That would mean that non-dir dentries would then have virtual children. You could then even use this to implement resource forks... Another alternative would be to note O_ALT and then skip pathwalk entirely, but just use the name as a key to the attribute, creating an anonfd to read it. But then why use openat() at all? You could instead do: metadatafd = openmeta(fd, "metadataname"); and save the page flag. You could even merge the two opens and do: metadatafd = openmeta("foo/bar", "metadataname"); Why not even combine this with Miklos's readfile() idea: readmeta(AT_FDCWD, "foo/bar", "metadataname", buf, sizeof(buf)); and we're now down to one syscall and no fds and you don't even need a magic filesystem to make it work. There's another consideration too: Paths are not unique handles to mounts. It's entirely possible to have colocated mounts. We need to be able to query all the mounts on a mountpoint. David