So supply a library of your own and try to convince people to use it
instead of libc.  You'll have to anyway, seeing that a large and

I agree. And in fact that is what we've been doing:

https://github.com/cyphar/libpathrs

I also plan on splitting the chase*() machinery in systemd out as
a separate C library as well:

https://github.com/systemd/systemd/blob/104750fd60da4c563650785e272a7ce0a6694d01/src/basic/chase.c#L238

hard-to-predict part of libc will be non-functional.  Which syscalls
are used by your library is entirely up to you.

Would that kind of thing added kernel-side assist the development of such
library?  Maybe, but I wouldn't bet too much on that - if you start from

It wouldn't really and we haven't needed it for that.