Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp3266124ybb; Tue, 31 Mar 2020 01:35:40 -0700 (PDT) X-Google-Smtp-Source: ADFU+vt5L6fjxcn+m8y1J3fDaQkAUq7kZskq+gEr0Omc0XfB12zC3Q1RRZVYlXjvvhZuMj2EOpyk X-Received: by 2002:aca:3008:: with SMTP id w8mr1262344oiw.96.1585643740664; Tue, 31 Mar 2020 01:35:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585643740; cv=none; d=google.com; s=arc-20160816; b=Pkkhg+Eyzq5twMMuAs7KEzDhJvICXaxXJqrGsPrDY2eAxOWtBPxUsc8zfyy5WI4qEA te9OSXLJiOuuKMsSvuCX/blndf5ARhADV414j5lSU3DFBTWW6HnX8thmmigzkrdNrwn2 /phKb0rGN2WXgLMtYii9KvnNyt6zBOUwDAgry3MU+/BMRBxPn00+uLYW647ApzDUtATc Gzdr3h+xm3Us0bxYpUcHucPC0Iv7nv3qr4b5UFt2f8CVXR9XT7D+QDAV4WAVgVBlEgto gM7mA3NLznBsEowhtn1zeepgjPsYED3wCudxgBE/BjwTxnmkTOy4u/EyuIYMl4IolNte mh1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=d3uoqh9h+iojx/+Rg3U0VTN2ulL9+wr9bMc1wrNA4m0=; b=SVF7rMKQXuLFJNVYXlnIwK/aPMMTfxgPgy2gt93+hm4wrGqoAgUGQNw7mA5lxWKWZO XRaHmIXJBmAwH0Cmz/59xRCp4Goh0B6sA1EJjEu1niEkWCSWmzmqRfvYUCvsLsNEdv8y 2wbwAd7Mj+Jvbo8/j52jvkOszRh28tepZZ9s4XBojMrSlDeOM63nmQEcXVWwibACRdiy s6Wjqe+Li3DKEXQ0IKIOWPiefAu5sj8Visi7+ZM+Cp8QKekDW53t7ptPPVHT++iw5Bnd cQLVyJhyjXGKaPOErf1fNltpmPvZ3TZ+8YQDTFPl0XPu8KGbnH7WH9/tWrbJHBqS9LR+ qYrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZW8Mu3de; 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=pass (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 u15si6878508ooq.37.2020.03.31.01.35.27; Tue, 31 Mar 2020 01:35:40 -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=@redhat.com header.s=mimecast20190719 header.b=ZW8Mu3de; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730161AbgCaIeq (ORCPT + 99 others); Tue, 31 Mar 2020 04:34:46 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:34324 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729624AbgCaIeq (ORCPT ); Tue, 31 Mar 2020 04:34:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585643684; 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=d3uoqh9h+iojx/+Rg3U0VTN2ulL9+wr9bMc1wrNA4m0=; b=ZW8Mu3deDP5e5GVq6IzQwBVRZSWhVnbJd8AoBCvhrBFiHceHSXPYCqyNtEA+W3mLWkpkag wi+jHJPfT6yJ+cHD6BncDH76PsK5tY3cd3Y2WjCXletUOvOk6ozu3Tu6/PsGNlwyynmAuc LYDj3pDJYNRpCFi8HHEBWdPqip3TgvE= 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-101-XwWS4oBAN9KvwkitkcQc6A-1; Tue, 31 Mar 2020 04:34:41 -0400 X-MC-Unique: XwWS4oBAN9KvwkitkcQc6A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 54B2B149C5; Tue, 31 Mar 2020 08:34:38 +0000 (UTC) Received: from ws.net.home (unknown [10.40.194.51]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1866096B80; Tue, 31 Mar 2020 08:34:33 +0000 (UTC) Date: Tue, 31 Mar 2020 10:34:30 +0200 From: Karel Zak To: Miklos Szeredi Cc: Christian Brauner , David Howells , Linus Torvalds , Al Viro , dray@redhat.com, Miklos Szeredi , Steven Whitehouse , Jeff Layton , Ian Kent , andres@anarazel.de, keyrings@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Lennart Poettering , Aleksa Sarai Subject: Re: Upcoming: Notifications, FS notifications and fsinfo() Message-ID: <20200331083430.kserp35qabnxvths@ws.net.home> References: <1445647.1585576702@warthog.procyon.org.uk> <20200330211700.g7evnuvvjenq3fzm@wittgenstein> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 31, 2020 at 07:11:11AM +0200, Miklos Szeredi wrote: > On Mon, Mar 30, 2020 at 11:17 PM Christian Brauner > wrote: > > > Fwiw, putting down my kernel hat and speaking as someone who maintains > > two container runtimes and various other low-level bits and pieces in > > userspace who'd make heavy use of this stuff I would prefer the fd-based > > fsinfo() approach especially in the light of across namespace > > operations, querying all properties of a mount atomically all-at-once, > > fsinfo(2) doesn't meet the atomically all-at-once requirement. I guess your /proc based idea have exactly the same problem... I see two possible ways: - after open("/mnt", O_PATH) create copy-on-write object in kernel to represent mount node -- kernel will able to modify it, but userspace will get unchanged data from the FD until to close() - improve fsinfo() to provide set (list) of the attributes by one call Karel -- Karel Zak http://karelzak.blogspot.com