Date: Sat, 09 Mar 2024 20:20:13 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Rick Macklem <rick.macklem@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, Jamie Landeg-Jones <jamie@catflap.org>, current@freebsd.org Subject: Re: Reason why "nocache" option is not displayed in "mount"? Message-ID: <32d3aed1d5632fbc43b8ec0f083ed90e@Leidinger.net> In-Reply-To: <CAM5tNy7A3Sa-QzUNJcZYVJXpB=MG_N6aKkoiUviTrU0nb2iq1Q@mail.gmail.com> References: <09bb45dea82d96c11f34cc48dda540dc@Leidinger.net> <202403072005.427K58KX014923@donotpassgo.dyslexicfish.net> <CANCZdfq2Z30jgh6Wt9Set=fZ271qr42Thy73YOxF=bh04R6Bfg@mail.gmail.com> <b8a9464bc6e371568579c316e1e48101@Leidinger.net> <CAM5tNy7A3Sa-QzUNJcZYVJXpB=MG_N6aKkoiUviTrU0nb2iq1Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--=_15e4e632b118ed346b5f64d4ad065209
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8;
format=flowed
Am 2024-03-09 15:27, schrieb Rick Macklem:
> On Sat, Mar 9, 2024 at 5:08 AM Alexander Leidinger
> <Alexander@leidinger.net> wrote:
>>
>> Am 2024-03-09 06:07, schrieb Warner Losh:
>>
>> > On Thu, Mar 7, 2024 at 1:05 PM Jamie Landeg-Jones <jamie@catflap.org>
>> > wrote:
>> >
>> >> Alexander Leidinger <Alexander@Leidinger.net> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> what is the reason why "nocache" is not displayed in the output of
>> >>> "mount" for nullfs options?
>> >>
>> >> Good catch. I also notice that "hidden" is not shown either.
>> >>
>> >> I guess that as for some time, "nocache" was a "secret" option, no-one
>> >> update "mount" to display it?
>> >
>> > So a couple of things to know.
>> >
>> > First, there's a list of known options. These are converted to a
>> > bitmask. This is then decoded and reported by mount. The other strings
>> > are passed to the filesystem directly. They decode it and do things,
>> > but they don't export them (that I can find). I believe that's why they
>> > aren't reported with 'mount'. There's a couple of other options in
>> > /etc/fstab that are pseudo options too.
>>
>> That's the technical explanation why it doesn't work. I'm a step
>> further
>> since initial mail, I even had a look at the code and know that
>> nocache
>> is recorded in a nullfs private flag and that the userland can not
>> access this (mount looks at struct statfs which doesn't provide info
>> to
>> this and some other things).
>>
>> My question was targeted more in the direction if there is a
>> conceptual
>> reason or if it was an oversight that it is not displayed. I admit
>> that
>> this was lost in translation...
>>
>> Regarding the issue of not being able to see all options which are in
>> effect for a given mount point (not specific to nocache): I consider
>> this to be a bug.
>> Pseudo options like "late" or "noauto" in fstab which don't make sense
>> to use when you use mount(8) a FS by hand, I do not consider here.
> As a data point, I added the "-m"option to nfsstat(1) so that all the
> nfs
> related options get displayed.
>
> Part of the problem is that this will be file system specific, since
> nmount()
> defers processing options to the file systems.
There exists values for a lot of the mount opions which are not
displayed. For example the nocache option for nullfs is
MNTK_NULL_NOCACHE in
https://cgit.freebsd.org/src/tree/sys/sys/mount.h#n515
This may not be useable as is, but I use it to show that there are
already bits public about it, just not in the proper place to be useful
to the userland.
Even FS specific options could be set as part of statfs (by letting the
FS set them in struct statfs). Or there could be a per-mount callback /
ioctl / whatever which provides the options in some way to the userland
if requested.
So we either have something which could be used but requires some
interface to let a FS set a value somewhere, or if this is a too gross
hack, we would need to come up with a new interface to query this info.
Bye,
Alexander.
--
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF
--=_15e4e632b118ed346b5f64d4ad065209
Content-Type: application/pgp-signature;
name=signature.asc
Content-Disposition: attachment;
filename=signature.asc;
size=833
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmXstnwACgkQEg2wmwP4
2IZPrA/8CyBuQDhcEzqqV206Bj9SfWZsObaLtDGdECsaVYcm0GEeqvIRT+DDYpWN
QyUOgMPAhJjACSGE2MCqqzINX8aUBQD7VnWnbhwao7coim5fE+UF+ruQ8NTqpSN6
P6Z7RCiuc7T8rvucbZBHc8dyxbj4u5fR62egzL3cgnblIEJzjYxLFrFD9jNFKwYb
8jdKNIMeiQg17cLYkJmm22vESLfnUxx6RKL9O9B0tuY6FoWumMawNg/4RtdSPgCZ
FjApQTQw09F977pnB5ZjlpcRTojv/DnCcTWr16NKJO6puY8i5PR4WyZfvQYrxhAg
Sj+HgKJRTYv0GR2IceZ1C7B56Y5C4EgOW6E8MljhO6QOYWVdiwsTouHV+kw+zsnC
3F0jm9+y57k8muzhHamfCIOV6duTCFUNsvPrlYww7QxlrcnQoYaTxgRK99qg3/jJ
7o4q7WiVuusVJ9yrkU+JGiq91emKw/U3kXmjvz7RFCn7oXUtWLlE+bOhXymuEj6F
UQzOuoz6QVO9EC/wpFmSJXrErVuU+zBR1BxIISAM+wJbjloXimyjqe7m303urexN
Lq0oGF1ZVP7p74+SD+9KF7liaE+HRsdBmJNW5C/IqpnpqOp8ir4RiuGftsglE5tP
wWf4gpnGShCxf134RmHjoGAttjPFhoxcjDCsxoNi6HNIZo5RxfY=
=0Vua
-----END PGP SIGNATURE-----
--=_15e4e632b118ed346b5f64d4ad065209--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32d3aed1d5632fbc43b8ec0f083ed90e>