From: Volker Weißmann Date: Tue, 3 Oct 2023 17:18:44 +0000 (+0200) Subject: Fix FORTIFY_SOURCE false positive X-Git-Tag: glibc-2.39~381 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7bb8045ec0595a031e68383849c3fbd9af134312;p=thirdparty%2Fglibc.git Fix FORTIFY_SOURCE false positive When -D_FORTIFY_SOURCE=2 was given during compilation, sprintf and similar functions will check if their first argument is in read-only memory and exit with *** %n in writable segment detected *** otherwise. To check if the memory is read-only, glibc reads frpm the file "/proc/self/maps". If opening this file fails due to too many open files (EMFILE), glibc will now ignore this error. Fixes [BZ #30932] Signed-off-by: Volker Weißmann Reviewed-by: Siddhesh Poyarekar --- diff --git a/sysdeps/unix/sysv/linux/readonly-area.c b/sysdeps/unix/sysv/linux/readonly-area.c index edc68873f6d..ba32372ebbb 100644 --- a/sysdeps/unix/sysv/linux/readonly-area.c +++ b/sysdeps/unix/sysv/linux/readonly-area.c @@ -42,7 +42,9 @@ __readonly_area (const char *ptr, size_t size) to the /proc filesystem if it is set[ug]id. There has been no willingness to change this in the kernel so far. */ - || errno == EACCES) + || errno == EACCES + /* Process has reached the maximum number of open files. */ + || errno == EMFILE) return 1; return -1; }