Re: Using the upcoming fsinfo()

[Ian Kent <raven@themaw.net>]

On Wed, 2019-05-22 at 10:59 +0800, Ian Kent wrote:
> 
> > 	This serves to workout that the call always returns what you 
> > expect it to, familiarity with the new call and how it works as well as
> > developing a first interface to construct and parse calls-to and 
> > output-from the call.
> 
> Avoiding having to parse string output (from the proc file system
> mount tables) is one of the key reasons to use a system call for
> this.
> 
> So this isn't the point of doing it.
> 
> The work for this (and some other new system calls) is being done
> in the kernel so the issue isn't to work out what the system call
> returns as much as it is to ensure the system call provides what's
> needed, implement things that aren't yet done and work out ways of
> providing things that are needed but can't yet be provided.

Just to give an idea of the amount of work that still needs to be
done there are around 70 file systems included in the Linux kernel
and, so far, the code needed to provide the file system specific
mount options via fsinfo() has been done for a little over 10 of
them (about 8 of these in the last few days) and most of those are
the simpler ones.

But having said that providing the file system specific mount options
appears to be one of only a couple of things that's missing.

Ian