[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+X7ob_Lc3OEmzUChCUAD-AFOtiVLNCQuqaNN1NJCH19LmiP0Q@mail.gmail.com>
Date: Thu, 30 Mar 2023 18:02:43 +0800
From: Matthias Görgens <matthias.goergens@...il.com>
To: musl@...ts.openwall.com
Subject: [BUG] hasmntopt weirdness
Musl's `hasmntopt` is a bit weird.
For example, my `/proc/mounts` contains the following line:
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k,inode64 0 0
If I run `hasmntopt(entp, "suid")` on that entry with glibc, I get
NULL. In musl I get: "suid,nodev,noexec,relatime,size=65536k,inode64".
Do we have a spec for what should happen? I can find multiple
descriptions online, some of them would allow what musl does, but not
all. I don't know what's authoritative.
Arguably the musl behaviour is a bit silly by itself, and would
actively cause bugs for someone porting programs from glibc.
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.
