about summary refs log tree commit diff
path: root/sysdeps/aarch64/fpu/log10f_sve.c
diff options
context:
space:
mode:
authorStefan Liebler <stli@linux.ibm.com>2023-12-13 12:44:50 +0100
committerStefan Liebler <stli@linux.ibm.com>2023-12-20 08:41:06 +0100
commit3150cc0c9019bf9da841419f86dda8e7f26d676d (patch)
tree3d49bd90f1ee04d140f2824bfd4e509ad5d11435 /sysdeps/aarch64/fpu/log10f_sve.c
parent50bef9bd63e7fb94f1d2cc8b7809256ffc73b2ef (diff)
downloadglibc-3150cc0c9019bf9da841419f86dda8e7f26d676d.tar.gz
glibc-3150cc0c9019bf9da841419f86dda8e7f26d676d.tar.xz
glibc-3150cc0c9019bf9da841419f86dda8e7f26d676d.zip
Fix elf/tst-env-setuid[-static] if test needs to be rerun.
If /tmp is mounted nosuid and make xcheck is run,
then tst-env-setuid fails UNSUPPORTED with "SGID failed: GID and EGID match"
and /var/tmp/tst-sonamemove-runmod1.so.profile is created.

If you then try to rerun the test with a suid mounted test-dir
(the SGID binary is created in test-dir which defaults to /tmp)
with something like that:
make tst-env-setuid-ENV="TMPDIR=..." t=elf/tst-env-setuid test
the test fails as the LD_PROFILE output file is still available
from the previous run.

Thus this patch removes the LD_PROFILE output file in parent
before spawning the SGID binary.

Even if LD_PROFILE is not supported anymore in static binaries,
use a different library and thus output file for tst-env-setuid
and tst-env-setuid-static in order to not interfere if both
tests are run in parallel.

Furthermore the checks in test_child are now more verbose.
Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
Diffstat (limited to 'sysdeps/aarch64/fpu/log10f_sve.c')
0 files changed, 0 insertions, 0 deletions