diff options
| author | Stafford Horne <shorne@gmail.com> | 2021-10-17 07:41:54 +0900 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-10-18 13:30:10 -0300 |
| commit | 06acd6d1d6f485f2751dcfec881044938742bc8e (patch) | |
| tree | a739da8d35582d3b6aaaa7c08d67b79ae9b7bf38 /sysdeps/unix/sysv/linux | |
| parent | 5118dcac68c4eadfd6304bb33adde63d062dc07f (diff) | |
| download | glibc-06acd6d1d6f485f2751dcfec881044938742bc8e.tar glibc-06acd6d1d6f485f2751dcfec881044938742bc8e.tar.gz glibc-06acd6d1d6f485f2751dcfec881044938742bc8e.tar.bz2 glibc-06acd6d1d6f485f2751dcfec881044938742bc8e.zip | |
nptl: Fix tst-cancel7 and tst-cancelx7 pidfile race
The check for waiting for the pidfile to be created looks wrong. At the
point when ACCESS is run the pid file will always be created and
accessible as it is created during DO_PREPARE. This means that thread
cancellation may be performed before the pid is written to the pidfile.
This was found to be flaky when testing on my OpenRISC platform.
Fix this by using the semaphore to wait for pidfile pid write
completion.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'sysdeps/unix/sysv/linux')
0 files changed, 0 insertions, 0 deletions