* Christian Brauner: > One difference to openat() is that openat2() doesn't silently ignore > unknown flags. But I'm not sure that would matter for iplementing > openat() via openat2() since there are no flags that openat() knows about > that openat2() doesn't know about afaict. So the only risks would be > programs that accidently have a bit set that isn't used yet. Will there be any new flags for openat in the future? If not, we can just use a constant mask in an openat2-based implementation of openat. Thanks, Florian
