[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegtRoXnPm5_sMYPL2L6FCZU52Tn8wk7NcW-dm4_2x=dD3Q@mail.gmail.com>
Date: Thu, 27 Feb 2020 10:36:38 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Ian Kent <raven@...maw.net>
Cc: Miklos Szeredi <mszeredi@...hat.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Steven Whitehouse <swhiteho@...hat.com>,
David Howells <dhowells@...hat.com>,
viro <viro@...iv.linux.org.uk>,
Christian Brauner <christian@...uner.io>,
Jann Horn <jannh@...gle.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Linux API <linux-api@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/17] VFS: Filesystem information and notifications [ver #17]
On Thu, Feb 27, 2020 at 6:06 AM Ian Kent <raven@...maw.net> 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
Powered by blists - more mailing lists