glibc/debug, branch vdso

support: Add FAIL test failure helper

2024-07-26T12:21:34Z

Add a FAIL test failure helper analogous to FAIL_RET, that does not cause the current function to return, providing a standardized way to report a test failure with a message supplied while permitting the caller to continue executing, for further reporting, cleaning up, etc. Update existing test cases that provide a conflicting definition of FAIL by removing the local FAIL definition and then as follows: - tst-fortify-syslog: provide a meaningful message in addition to the file name already added by ; 'support_record_failure' is already called by 'support_print_failure_impl' invoked by the new FAIL test failure helper. - tst-ctype: no update to FAIL calls required, with the name of the file and the line number within of the failure site additionally included by the new FAIL test failure helper, and error counting plus count reporting upon test program termination also already provided by 'support_record_failure' and 'support_report_failure' respectively, called by 'support_print_failure_impl' and 'adjust_exit_status' also respectively. However in a number of places 'printf' is called and the error count adjusted by hand, so update these places to make use of FAIL instead. And last but not least adjust the final summary just to report completion, with any error count following as reported by the test driver. - test-tgmath2: no update to FAIL calls required, with the name of the file of the failure site additionally included by the new FAIL test failure helper. Also there is no need to track the return status by hand as any call to FAIL will eventually cause the test case to return an unsuccesful exit status regardless of the return status from the test function, via a call to 'adjust_exit_status' made by the test driver. Reviewed-by: DJ Delorie

Unify output from backtrace_symbols_fd with backtrace_symbols (bug 31730)

2024-05-14T10:55:06Z

string: Add hidden builtin definition for __strcpy_chk.

2024-02-06T08:17:04Z

Otherwise on at least x86_64 and s390x there is an unwanted PLT entry in libc.so when configured with --enable-fortify-source=3 and build with -Os. This is observed in elf/check-localplt Extra PLT reference: libc.so: __strcpy_chk The call to PLT entry is in inet/ruserpass.c. Reviewed-by: Adhemerval Zanella

debug/getwd_chk.c: warning should be emitted for the __getwd_chk symbol.

2024-01-12T14:21:26Z

Otherwise the warning message for the getwd symbol ends up being duplicated. Signed-off-by: Frederic Cambus Reviewed-by: Adhemerval Zanella Signed-off-by: Andreas K. Hüttel

Update copyright dates not handled by scripts/update-copyrights

2024-01-01T18:53:40Z

I've updated copyright dates in glibc for 2024. This is the patch for the changes not generated by scripts/update-copyrights and subsequent build / regeneration of generated files.

Update copyright dates with scripts/update-copyrights

2024-01-01T18:53:40Z

debug: Add fortify wprintf tests

2023-12-29T13:57:27Z

Similar to other printf-like ones. It requires to be in a different process so we can change the orientation of stdout. Checked on aarch64, armhf, x86_64, and i686.

debug: Add fortify syslog tests

2023-12-29T13:57:03Z

It requires to be in a container tests to avoid logging bogus information on the system. The syslog also requires to be checked in a different process because the internal printf call will abort with the internal syslog lock taken (which makes subsequent syslog calls deadlock). Checked on aarch64, armhf, x86_64, and i686. Reviewed-by: Siddhesh Poyarekar

debug: Add fortify dprintf tests

2023-12-29T13:57:03Z

Similar to other printf-like ones. Checked on aarch64, armhf, x86_64, and i686. Reviewed-by: Siddhesh Poyarekar

debug: Increase tst-fortify checks for compiler without __va_arg_pack support

2023-12-29T13:57:03Z

The fortify wrappers for varargs functions already add fallbacks to builtins calls if __va_arg_pack is not supported. Checked on aarch64, armhf, x86_64, and i686. Reviewed-by: Siddhesh Poyarekar