Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp901878ybf; Thu, 27 Feb 2020 01:38:17 -0800 (PST) X-Google-Smtp-Source: APXvYqzkU4wejqhRyoRscjQBQIl+dVJ2EteMyFAafM7u7emCIFI/QlofOLFi9jmB9CYtM4dAHlvI X-Received: by 2002:a05:6830:194:: with SMTP id q20mr2669194ota.92.1582796297032; Thu, 27 Feb 2020 01:38:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582796297; cv=none; d=google.com; s=arc-20160816; b=h/3chZcq9UJ7KShUZofDF5Is7G6Uo1owqxLm+s5L3eZkjRMYRkOOIvwJLU0Q7BzGv1 cFYEP+Ay4OL4aO8sURGPZi661b5VFmaBgUgwUeWspyvKbXIZcnIjrUlTJu0mwc1Fvt0z XjrYAMBwjUkbX97yEET2pUykv9uCnWQ/WDoxgCZknIYI6zjB3u3Gl1CaFOlcKQsoptJc 8pEFnkHbNoz1qlbmpAx3V7Qgl7v3BfDYkwabpJxyFg2DVZ5blTRNs7r3PDIEjTHkC2D1 YIdXG7Wos+fZKB9IlxGh/T4ItM+aeMn1RZPlVeCcPTMjg2hcywZ7hXR98kH/ZlHvbvun IohA== 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=TSFAYumXnIb4mNx6pb9jSCJtikoAu1fiU5AFDR41HiM=; b=bohk+0HYofYUMAUeRC4tXgmqz16mN61Q+yNW3V1bMfv/m+koK/FztVqwIbfUB91885 ROB1cGNUhqu/7O+setDtih95IAtWWogNCKW7MkNIlIjBFQ3gEs8WdK51MhAeBewOhDio AVOH5HyULCLUEHJ+xaFz9qbbUmtpYfBAdgTPxBSS2/t/GzV7Omaj4XH08Xlv7oX7iFAA ubZpUnB91KnfeMOfjlPGzCZ9ImsGPfRg3rpN0rokhxqgUZ12ROPyArXxPtWBtenqSYZh 6tKzGP/o9heZ3MU2sA/w86wBLMiMiuY0kFLZod9v8xMw9A72S0xzLm/oSuCuPjESJOtn TUFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@szeredi.hu header.s=google header.b="nMST/l5y"; 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 m4si1187275otr.268.2020.02.27.01.38.03; Thu, 27 Feb 2020 01:38:17 -0800 (PST) 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=temperror (no key for signature) header.i=@szeredi.hu header.s=google header.b="nMST/l5y"; 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 S1728698AbgB0Jgu (ORCPT + 99 others); Thu, 27 Feb 2020 04:36:50 -0500 Received: from mail-io1-f66.google.com ([209.85.166.66]:41227 "EHLO mail-io1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728624AbgB0Jgt (ORCPT ); Thu, 27 Feb 2020 04:36:49 -0500 Received: by mail-io1-f66.google.com with SMTP id m25so2439967ioo.8 for ; Thu, 27 Feb 2020 01:36:49 -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=TSFAYumXnIb4mNx6pb9jSCJtikoAu1fiU5AFDR41HiM=; b=nMST/l5yp4EsOlkQkjz+oyXVo6tR4nbd5GbUbI5x84hWOMcXm3M7y8DV6kt66nn7b7 GIlsjbkbx3vQijL/6+LHbt8H5ZHfFqOOXohYBjwIMdjJnBLoeC35oZ4Yl225QYdACe5/ kVd9f5v/M5gtnQTRoS4CTQDPAYtlf8yBp6HVk= 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=TSFAYumXnIb4mNx6pb9jSCJtikoAu1fiU5AFDR41HiM=; b=tZX76oCxLJ0hyo4fB8W3XT7n/6yKAhfkPeByl6QAxHJw2XEczrLsss7nPJOfKu8SC+ UAklbX0AIw22WV5DHGbfsYqlGNDDq/UnON0axU0IzQuvR8nC41STdT17XBqZu+YPwaSX VcGSA26sbyVReiPnwOtLEbifj+zBixzATb0QByv6rRwc9xZSpZfIy+Zirh1VeK9YCOcP T0HGcAn4Mp6S8uXmKfr5cGHMfko25in+wa4/TnsQn875axlarAHwuvyXRekO6trBgDxQ hSj2ULkgN9d2e577ZjPFGznBrBG6a2v5mSaQkYknDn4Nh6+klerkMbfu3xHgtxfcDJGc ek/g== X-Gm-Message-State: APjAAAXy5D5NqQ61xOkTB5N1ozNbFkrRJMhgimYtiYNEISsccMrBGTff 767EpWSovio+EbE3MbXaSsIZhbmYLZDLwzUcjo7bag== X-Received: by 2002:a05:6602:382:: with SMTP id f2mr3597157iov.174.1582796209051; Thu, 27 Feb 2020 01:36:49 -0800 (PST) MIME-Version: 1.0 References: <158230810644.2185128.16726948836367716086.stgit@warthog.procyon.org.uk> <1582316494.3376.45.camel@HansenPartnership.com> <1582556135.3384.4.camel@HansenPartnership.com> <1582644535.3361.8.camel@HansenPartnership.com> <1c8db4e2b707f958316941d8edd2073ee7e7b22c.camel@themaw.net> In-Reply-To: <1c8db4e2b707f958316941d8edd2073ee7e7b22c.camel@themaw.net> From: Miklos Szeredi Date: Thu, 27 Feb 2020 10:36:38 +0100 Message-ID: Subject: Re: [PATCH 00/17] VFS: Filesystem information and notifications [ver #17] To: Ian Kent Cc: Miklos Szeredi , James Bottomley , Steven Whitehouse , David Howells , viro , Christian Brauner , Jann Horn , "Darrick J. Wong" , Linux API , linux-fsdevel , lkml 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 Thu, Feb 27, 2020 at 6:06 AM Ian Kent wrote: > At the least the question of "do we need a highly efficient way > to query the superblock parameters all at once" needs to be > extended to include mount table enumeration as well as getting > the info. > > But this is just me thinking about mount table handling and the > quite significant problem we now have with user space scanning > the proc mount tables to get this information. Right. So the problem is that currently autofs needs to rescan the proc mount table on every change. The solution to that is to - add a notification mechanism - and a way to selectively query mount/superblock information right? For the notification we have uevents in sysfs, which also supplies the changed parameters. Taking aside namespace issues and addressing mounts would this work for autofs? Thanks, Miklos