Should legacy fstat (via __fxstat) and fstat@GLIBC_2.33 call the same syscall?

[Florian Weimer]

Currently, __fxstat may get mapped to the fstat system call, while fstat
goes to fstatat.  This makes sandboxing issues less obvious to debug:

  <https://bugs.chromium.org/p/chromium/issues/detail?id=1164975>

Should we change this before the release?  And if yes, in what
direction?

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill