From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 66929C10F00 for ; Sat, 7 Mar 2020 20:48:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3C78E2070A for ; Sat, 7 Mar 2020 20:48:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=szeredi.hu header.i=@szeredi.hu header.b="PV3bf2R9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726292AbgCGUst (ORCPT ); Sat, 7 Mar 2020 15:48:49 -0500 Received: from mail-il1-f196.google.com ([209.85.166.196]:36619 "EHLO mail-il1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726269AbgCGUst (ORCPT ); Sat, 7 Mar 2020 15:48:49 -0500 Received: by mail-il1-f196.google.com with SMTP id b17so5270294iln.3 for ; Sat, 07 Mar 2020 12:48:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZlaiWBNqvrdyvkEefn9yJWjZp7C2bAb1YLICnuJhP8I=; b=PV3bf2R9X3sQruGbBjzJvFY4AOshOxYvj+SiyibH20IZIQwjIExrhsqLUFM6P6R+lL LrAJRQjI/qJXCe04P0VvuJgkt9vJeW2qTNk71iIlLi/SHzLO0MvLutNTnfsD4TjmaXrj pun1BhXPZ65cZKYbR1qBfSXAyqWEqWfjqbGtM= 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=ZlaiWBNqvrdyvkEefn9yJWjZp7C2bAb1YLICnuJhP8I=; b=eYEXFyuLzO1GZjwP++ld/5M0K5ps7rxjLxRzjC/ItciKNyZ8LacX0fRh/jJWcPDT5t 9e2MIESKVVOAHDvW3jG3VaAQIwWF+oLx/sP8/AAbMcx9HN7kEuqU4u3NAFmb3bzA/m5c 6/mzl/quVnq2WMQLD+fFQ/b7ux2zpPB/gqjQ9YiR0ChWyFZGUJdfTGYeZ+/q1qNKf6v9 2ub9RVqYtS/vTcqswRTTCbOVQLCL2HfMUoTVQKsAfXCtfmK78VManTS9/JQi29SCvaQ9 Us7Kh3ILtexxJ2RgJLQzG13Bv+gIV7pqAmSEZUE2bqicrAjq2nQXOJN/hc8pkpyNMQUQ EhYw== X-Gm-Message-State: ANhLgQ3lEcU8B/uG86pn6Q5fcOVP7S4xI5edR9UP3GyBwLblev0hzUqP 7BvshT3ajldjLUcT8VdCcf8lQ+YQ85FC8yTk1LFLzw== X-Google-Smtp-Source: ADFU+vskwVXCTzkhh+ZXd7Wbqe2WHoM17S7U48HvUGcGrtwnAQOiiNlg5R1xofLf5jp6bJ1vVeTIGj3wJCAenoDZ5x8= X-Received: by 2002:a92:d745:: with SMTP id e5mr8793655ilq.285.1583614126795; Sat, 07 Mar 2020 12:48:46 -0800 (PST) MIME-Version: 1.0 References: <1582556135.3384.4.camel@HansenPartnership.com> <1582644535.3361.8.camel@HansenPartnership.com> <20200228155244.k4h4hz3dqhl7q7ks@wittgenstein> <107666.1582907766@warthog.procyon.org.uk> <0403cda7345e34c800eec8e2870a1917a8c07e5c.camel@themaw.net> <20200306162549.GA28467@miu.piliscsaba.redhat.com> <20200307094834.GA3888906@kroah.com> In-Reply-To: <20200307094834.GA3888906@kroah.com> From: Miklos Szeredi Date: Sat, 7 Mar 2020 21:48:35 +0100 Message-ID: Subject: Re: [PATCH 00/17] VFS: Filesystem information and notifications [ver #17] To: Greg Kroah-Hartman Cc: Ian Kent , David Howells , Christian Brauner , James Bottomley , Steven Whitehouse , Miklos Szeredi , viro , Christian Brauner , Jann Horn , "Darrick J. Wong" , Linux API , linux-fsdevel , lkml Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Sat, Mar 7, 2020 at 10:48 AM Greg Kroah-Hartman wrote: > > On Fri, Mar 06, 2020 at 05:25:49PM +0100, Miklos Szeredi wrote: > > On Tue, Mar 03, 2020 at 08:46:09AM +0100, Miklos Szeredi wrote: > > > > > > I'm doing a patch. Let's see how it fares in the face of all these > > > preconceptions. > > > > Here's a first cut. Doesn't yet have superblock info, just mount info. > > Probably has rough edges, but appears to work. > > > > I started with sysfs, then kernfs, then went with a custom filesystem, because > > neither could do what I wanted. > > Hm, what is wrong with kernfs that prevented you from using it here? > Just complexity or something else? I wanted to have a single instance covering all the namespaces, with just a filtered view depending on which namespace the task is looking at it. Having a kernfs_node for each attribute is also rather heavy compared to the size of struct mount. Thanks, Miklos