glibc.git/rt, branch zack/remove-libcrypt

Exclude routines from fortification

2023-07-05T14:59:48+00:00

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

rt/tst-mqueue4.c: Fix wrong number of argument for mq_open

2023-06-22T04:21:13+00:00

The mq_open routine should only get either 2 or 4 arguments, this test
wrongly passed 3.

Reviewed-by: Siddhesh Poyarekar

Fix all the remaining misspellings -- BZ 25337

2023-06-02T01:39:48+00:00

tests: replace write by xwrite

2023-06-01T16:40:05+00:00

Using write without cheks leads to warn unused result when __wur is
enabled.

Reviewed-by: Siddhesh Poyarekar

aio: Fix freeing memory

2023-04-11T22:14:08+00:00

The content of the pool array is initialized only until pool_size,
pointers between pool_size and pool_max_size were not initialized by the
realloc call in get_elem so they should not be freed.

This fixes aio tests crashing at their termination on GNU/Hurd.

Move libc_freeres_ptrs and libc_subfreeres to hidden/weak functions

2023-03-27T16:57:55+00:00

They are both used by __libc_freeres to free all library malloc
allocated resources to help tooling like mtrace or valgrind with
memory leak tracking.

The current scheme uses assembly markers and linker script entries
to consolidate the free routine function pointers in the RELRO segment
and to be freed buffers in BSS.

This patch changes it to use specific free functions for
libc_freeres_ptrs buffers and call the function pointer array directly
with call_function_static_weak.

It allows the removal of both the internal macros and the linker
script sections.

Checked on x86_64-linux-gnu, i686-linux-gnu, and aarch64-linux-gnu.
Reviewed-by: Carlos O'Donell

rt: fix shm_open not set ENAMETOOLONG when name exceeds {_POSIX_PATH_MAX}

2023-03-08T13:11:54+00:00

according to man-pages-posix-2017, shm_open() function may fail if the length
of the name argument exceeds {_POSIX_PATH_MAX} and set ENAMETOOLONG

Signed-off-by: abushwang 
Reviewed-by: Adhemerval Zanella

hurd: Implement SHM_ANON

2023-02-01T22:36:11+00:00

This adds a special SHM_ANON value that can be passed into shm_open ()
in place of a name. When called in this way, shm_open () will create a
new anonymous shared memory file. The file will be created in the same
way that other shared memory files are created (i.e., under /dev/shm/),
except that it is not given a name and therefore cannot be reached from
the file system, nor by other calls to shm_open (). This is accomplished
by utilizing O_TMPFILE.

This is intended to be compatible with FreeBSD's API of the same name.

Signed-off-by: Sergey Bugaev 
Message-Id: <20230130125216.6254-4-bugaevc@gmail.com>

Update copyright dates with scripts/update-copyrights

2023-01-06T21:14:39+00:00

rt: Initialize mq_send input on tst-mqueue{5,6}

2022-10-05T21:04:13+00:00

GCC with -Os warns that the mq_send input may be used uninitialized.
Although for the tests the data content sent is not important, since
both tests checks only if mq_notify was properly set, the warning is
correct and data is indeed uninitialized.

Checked on x86_64-linux-gnu and i686-linux-gnu.
Reviewed-by: Carlos O'Donell 
Tested-by: Carlos O'Donell