public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Frederic Berat <fberat@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] libio/bits/stdio2-decl.h: Avoid PLT entries with _FORTIFY_SOURCE
Date: Wed,  5 Jul 2023 15:05:36 +0000 (GMT)	[thread overview]
Message-ID: <20230705150536.F0CD23857014@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=923b53e920ad069599ca691dbab477ae26d6f02b

commit 923b53e920ad069599ca691dbab477ae26d6f02b
Author: Frédéric Bérat <fberat@redhat.com>
Date:   Wed Jun 28 09:08:44 2023 +0200

    libio/bits/stdio2-decl.h: Avoid PLT entries with _FORTIFY_SOURCE
    
    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>

Diff:
---
 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));

                 reply	other threads:[~2023-07-05 15:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230705150536.F0CD23857014@sourceware.org \
    --to=fberat@sourceware.org \
    --cc=glibc-cvs@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).