about summary refs log tree commit diff
path: root/sysdeps/pthread/tst-flock1.c
diff options
context:
space:
mode:
authorFrédéric Bérat <fberat@redhat.com>2023-06-14 10:52:06 +0200
committerSiddhesh Poyarekar <siddhesh@sourceware.org>2023-06-19 09:14:56 -0400
commit20b6b8e8a50874dd189687df8f6f8a11d4813b34 (patch)
treedadbbe8e8c05cf8a9c647b9c9b3198c086fec475 /sysdeps/pthread/tst-flock1.c
parentcf30aa43a5917f441c9438aaee201c53c8e1d76b (diff)
downloadglibc-20b6b8e8a50874dd189687df8f6f8a11d4813b34.tar.gz
glibc-20b6b8e8a50874dd189687df8f6f8a11d4813b34.tar.xz
glibc-20b6b8e8a50874dd189687df8f6f8a11d4813b34.zip
tests: replace read by xread
With fortification enabled, read calls return result needs to be checked,
has it gets the __wur macro enabled.

Note on read call removal from  sysdeps/pthread/tst-cancel20.c and
sysdeps/pthread/tst-cancel21.c:
It is assumed that this second read call was there to overcome the race
condition between pipe closure and thread cancellation that could happen
in the original code. Since this race condition got fixed by
d0e3ffb7a58854248f1d5e737610d50cd0a60f46 the second call seems
superfluous. Hence, instead of checking for the return value of read, it
looks reasonable to simply remove it.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Diffstat (limited to 'sysdeps/pthread/tst-flock1.c')
0 files changed, 0 insertions, 0 deletions