fortify-headers/include/string.h, branch experimental

Add a missing FORTIFY_PEDANTIC_CHECKS

2025-10-28T22:18:21Z

Fixing the following issue: ``` In file included from xstrndup.c:34: /OpenWrt/aarch64/staging_dir/toolchain-aarch64_cortex-a53_gcc-14.3.0_musl/include/fortify/string.h: In function 'mempcpy': /OpenWrt/aarch64/staging_dir/toolchain-aarch64_cortex-a53_gcc-14.3.0_musl/include/fortify/string.h:340:13: error: 'nonnull' argument '__d' compared to NULL [-Werror=nonnull-compare] 340 | if (!__d || !__s) | ^~~~ /OpenWrt/aarch64/staging_dir/toolchain-aarch64_cortex-a53_gcc-14.3.0_musl/include/fortify/string.h:340:21: error: 'nonnull' argument '__s' compared to NULL [-Werror=nonnull-compare] 340 | if (!__d || !__s) | ^~~~ cc1: all warnings being treated as errors make[5]: *** [Makefile:511: xstrndup.o] Error 1 ``` Reported in https://github.com/openwrt/openwrt/pull/20552

Use C90-compliant comments

2025-10-28T22:13:42Z

Check if FORTIFY_USE_NATIVE_CHK is defined

2025-10-28T17:12:50Z

The previews code tried to get the value defined for FORTIFY_USE_NATIVE_CHK and this resulted in some build errors like this: ``` /include/fortify/stdio.h: In function 'vsnprintf': /include/fortify/stdio.h:155:49: error: "FORTIFY_USE_NATIVE_CHK" is not defined, evaluates to 0 [-Werror=undef] 155 | #if __has_builtin(__builtin___vsnprintf_chk) && FORTIFY_USE_NATIVE_CHK | ^~~~~~~~~~~~~~~~~~~~~~ ``` Check if it is defined instead. Signed-off-by: Hauke Mehrtens

Bump actions/upload-pages-artifact from v1 to v3

2025-05-12T16:52:20Z

Neuter an issue in strncat

2024-10-21T13:04:50Z

`strlen(src)` isn't guaranteed to be valid.

Fix a crash in strncpy/stpncpy

2024-10-10T13:50:40Z

``` Core was generated by `scripts/mod/modpost -M -m -o Module.symvers -n -T modules.order vmlinux.o'. Program terminated with signal SIGSEGV, Segmentation fault. warning: 17 src/string/strlen.c: No such file or directory (gdb) bt ``` > I think strncpy logic is broken: `__fh_size_t max_len_s = strlen(__s);` may try read past `size_t __n`. > Create a buf without any trailing `\0`, do `strncpy(dest, buf, sizeof(buf));`, it should work, since `strncpy` will stop at `sizeof buf` > but the current fority-headers implementation will do `strlen(buf)`, which will go boom when it is not terminated with \0 Reported-by: ncopa

Fix usage of strnlen

2024-10-03T22:16:50Z

As with previous commit, some strnlen calls where introduced in 22a8094, but not reverted. As strnlen isn't part of C standard, this was breaking C builds.

Revert d2594298b89d0fb8989cae3ebc8900e77b6aa478

2024-09-02T14:11:06Z

As reported on irc: ``` 17:51 jvoisin, fortify-headers seems to be broken (on Alpine at least) 17:52 Repeating the message from over-there: 17:52 /usr/include/fortify/string.h: In function 'strncat': 17:52 /usr/include/fortify/string.h:297:36: error: implicit declaration of function 'strnlen'; did you mean 'strlen'? [-Wimplicit-function-declaration] 17:52 This is with a simple file that includes string.h and call strncat, built with c99 -O1 f.c ```

Fix access annotation for stpncpy/strncpy

2024-07-10T14:46:15Z

The dsize parameter is the length of the dst, not the length of the src. Reported-by: ncopa

prefix special defines with FORTIFY_

2024-07-10T13:20:23Z

just in case, and because 'PEDANTIC_CHECKS' is a really generic name