On 2025-08-28 01:42, Aleksa Sarai wrote:
I still fail to understand how a hypothetical "give me the supported flags"
openat2 flag would be useful enough to justify complicating the openat2 API
today.
My only concern is that it would break recompiles if/when we change it
back.
OK, but from what I can see there's no identified possibility that
openat2 will modify the objects its arguments point to, just as there's
no identified possibility that plain openat will do so (in a
hypothetical extension to remove unnecessary slashes from its filename
argument, say).
In that case it's pretty clear that glibc should mark the open_how
argument as pointer-to-const, just as glibc already marks the filename
argument.
