glibc/libio/Makefile, branch master

libio: handle opening a file when all files are closed (bug 31963)

2024-07-09T08:12:36Z

_IO_list_all becomes NULL when all files (including standard files) are closed.

Fix conditionals on mtrace-based tests (bug 31892)

2024-07-01T15:20:30Z

The conditionals for several mtrace-based tests in catgets, elf, libio, malloc, misc, nptl, posix, and stdio-common were incorrect leading to test failures when bootstrapping glibc without perl. The correct conditional for mtrace-based tests requires three checks: first checking for run-built-tests, then build-shared, and lastly that PERL is not equal to "no" (missing perl). Reviewed-by: Adhemerval Zanella

libio: Test for fdopen memory leak without SEEK_END support (bug 31840)

2024-06-04T14:09:33Z

The bug report used /dev/mem, but /proc/self/mem works as well (if available).

Add crt1-2.0.o for glibc 2.0 compatibility tests

2024-05-06T14:49:40Z

Starting from glibc 2.1, crt1.o contains _IO_stdin_used which is checked by _IO_check_libio to provide binary compatibility for glibc 2.0. Add crt1-2.0.o for tests against glibc 2.0. Define tests-2.0 for glibc 2.0 compatibility tests. Add and update glibc 2.0 compatibility tests for stderr, matherr and pthread_kill. Reviewed-by: Carlos O'Donell

libio: Sort test variables in Makefile

2024-04-30T16:43:20Z

Sort test variables in libio/Makefile using scripts/sort-makefile-lines.py. Reviewed-by: Sunil K Pandey

Update copyright dates with scripts/update-copyrights

2024-01-01T18:53:40Z

Exclude routines from fortification

2023-07-05T14:59:48Z

Since the _FORTIFY_SOURCE feature uses some routines of Glibc, they need to be excluded from the fortification. On top of that: - some tests explicitly verify that some level of fortification works appropriately, we therefore shouldn't modify the level set for them. - some objects need to be build with optimization disabled, which prevents _FORTIFY_SOURCE to be used for them. Assembler files that implement architecture specific versions of the fortified routines were not excluded from _FORTIFY_SOURCE as there is no C header included that would impact their behavior. Reviewed-by: Siddhesh Poyarekar

libio: Remove the usage of __libc_IO_vtables

2023-03-27T16:57:55Z

Instead of using a special ELF section along with a linker script directive to put the IO vtables within the RELRO section, the libio vtables are all moved to an array marked as data.relro (so linker will place in the RELRO segment without the need of extra directives). To avoid static linking namespace issues and including all vtable referenced objects, all required function pointers are set to weak alias. Checked on x86_64-linux-gnu, i686-linux-gnu, and aarch64-linux-gnu. Reviewed-by: Carlos O'Donell

Update copyright dates with scripts/update-copyrights

2023-01-06T21:14:39Z

getdelim: ensure error indicator is set on error (bug 29917)

2023-01-02T09:58:49Z

POSIX requires that getdelim and getline set the error indicator on the stream when an error occured, in addition to setting errno.