From: "Frédéric Bérat" <fberat@redhat.com>
To: libc-alpha@sourceware.org
Cc: siddhesh@gotplt.org, fberat@redhat.com,
Siddhesh Poyarekar <siddhesh@sourceware.org>
Subject: [PATCH v5 13/14] libio/bits/stdio2-decl.h: Avoid PLT entries with _FORTIFY_SOURCE
Date: Wed, 5 Jul 2023 16:10:48 +0200 [thread overview]
Message-ID: <20230705141055.274575-14-fberat@redhat.com> (raw)
In-Reply-To: <20230705141055.274575-1-fberat@redhat.com>
The change is meant to avoid unwanted PLT entry for the fgets_unlocked
routine when _FORTIFY_SOURCE is set.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
---
libio/bits/stdio2-decl.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libio/bits/stdio2-decl.h b/libio/bits/stdio2-decl.h
index 114b06d24b..d7ef7283d6 100644
--- a/libio/bits/stdio2-decl.h
+++ b/libio/bits/stdio2-decl.h
@@ -122,7 +122,7 @@ extern size_t __fread_chk (void *__restrict __ptr, size_t __ptrlen,
FILE *__restrict __stream) __wur;
#ifdef __USE_GNU
-extern char *__REDIRECT (__fgets_unlocked_alias,
+extern char *__REDIRECT_FORTIFY (__fgets_unlocked_alias,
(char *__restrict __s, int __n,
FILE *__restrict __stream), fgets_unlocked)
__wur __attr_access ((__write_only__, 1, 2));
--
2.41.0
next prev parent reply other threads:[~2023-07-05 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:10 [PATCH v5 00/14] Allow glibc to be built " Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 01/14] " Frédéric Bérat
2023-07-05 14:30 ` Siddhesh Poyarekar
2023-07-05 14:10 ` [PATCH v5 02/14] Exclude routines from fortification Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 03/14] sysdeps: Ensure ieee128*_chk routines to be properly named Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 04/14] string: Ensure *_chk routines have their hidden builtin definition available Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 05/14] stdio: " Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 06/14] misc/sys/cdefs.h: Create FORTIFY redirects for internal calls Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 07/14] wchar: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 08/14] posix/bits/unistd.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 09/14] unistd: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 10/14] misc/bits/select2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 11/14] misc/bits/syslog.h: Clearly separate declaration from definition Frédéric Bérat
2023-07-05 14:10 ` [PATCH v5 12/14] libio/bits/stdio2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:10 ` Frédéric Bérat [this message]
2023-07-05 14:10 ` [PATCH v5 14/14] sysdeps/ieee754/ldbl-128ibm-compat: Fix warn unused result Frédéric Bérat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230705141055.274575-14-fberat@redhat.com \
--to=fberat@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
--cc=siddhesh@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).