[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <D7J7LY9HK54W.1RVKG5JUCLSNT@posteo.net>
Date: Mon, 03 Feb 2025 23:46:06 +0000
From: "Sertonix" <sertonix@...teo.net>
To: <musl@...ts.openwall.com>
Subject: hasmntopt(3) match options instead of substring?
Hi,
people reported issues with mount options not working correctly with
ZFS[1] and someone noticed that it could be related to a behaviour
difference of hasmntopt(3) between musl and glibc.
The manpage[2] mentions that it returns a "substring that matches opt".
Just like musl has implemented it this is just strstr. The problem is
that it will return "atime" as a option found in "noatime" even though
that is probably not what people want.
glibc only accepts matches that match the complete option name.[3]
Would it be possible for musl to only match options as well?
Ideally the wording of hasmntopt(3) would be improved too.
[1]: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12382
[2]: https://man.archlinux.org/man/hasmntopt.3.en
[3]: https://codebrowser.dev/glibc/glibc/misc/mntent_r.c.html#__hasmntopt
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
