On Fri, Mar 24, 2023 at 01:39:09PM +0800, Ian Kent wrote:
> Karel do you find what I'm saying is accurate?
> Do you think we will be able to get rid of the sloppy option over
> time with the move to use the mount API?
The question is what we're talking about :-)
For mount(8) and libmount, there is nothing like the "sloppy" mount option.
If you use it in your fstab or as "mount -o sloppy" on the command line,
then it's used as any other fs-specific mount option; the library copies
the string to mount(2) or fsconfig(2) syscall. The library has no clue
what the string means (it's the same as "mount -o foobar").
But there is another "sloppy" :-) The command line argument, "mount -s".
This argument is not internally used by libmount or mount(8), but it's
repeated on /sbin/mount.<type> command lines (e.g., "mount -t nfs -s"
means "/sbin/mount.nfs -s").
I guess more interesting is mount.nfs, where both "-s" and "sloppy" lives
together. The mount.nfs uses this option to be tolerant when parsing mount
options string, and it also seems it converts "-s" to "sloppy" string for
mount syscall.
So, for mount(8)/libmount, digging a grave for the "sloppy" will be trivial.
All I need is to add a note about depreciation to the man page and later
remove "-s" from /sbin/mount.<type> command line.
SteveD (in CC:) will comment on it from the NFS point of view because the
real fun happens there :-)
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
