Some configuration (for instance default docker ubuntu images) uses
a default empty and invalid /etc/fstab configuration file. It makes
any call to getmntent return NULL and it leads to failures on
Msan-aarch64{-with-call}-Test/MemorySanitizer.getmntent{_r}.
This patch fixes it by creating a temporary file with some valid
entries (although not valid for the system) to use along with
setmntent/getmntent.
Either make this a constructor, or call it from the constructor, or add a check in the destructor so that it does not try to unlink an uninitialized path if Create was never called.
What happens if the test fails in one of the ASSERTs, will the file be unlinked? We build msan tests with -fno-exceptions.