glibc.git/support/xread.c, branch master Unnamed repository; edit this file 'description' to name the repository. Update copyright dates with scripts/update-copyrights 2025-01-01T19:22:09+00:00 Paul Eggert eggert@cs.ucla.edu 2025-01-01T18:14:45+00:00 2642002380aafb71a1d3b569b6d7ebeab3284816 






Update copyright dates with scripts/update-copyrights
2024-01-01T18:53:40+00:00

Paul Eggert
eggert@cs.ucla.edu

2024-01-01T18:12:26+00:00

dff8da6b3e89b986bb7f6b1ec18cf65d5972e307












tests: replace read by xread
2023-06-19T13:14:56+00:00

Frédéric Bérat
fberat@redhat.com

2023-06-14T08:52:06+00:00

20b6b8e8a50874dd189687df8f6f8a11d4813b34

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>





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>