public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-stable@sourceware.org
Cc: carlos@redhat.com, fweimer@redhat.com
Subject: [committed 2.34 0/8] _FORTIFY_SOURCE=3 and fixes
Date: Fri, 11 Mar 2022 20:41:55 +0530	[thread overview]
Message-ID: <20220311151203.3585163-1-siddhesh@sourceware.org> (raw)

Backport _FORTIFY_SOURCE=3 support for gcc 12 into 2.34 along with testing
improvements and miscellaneous fixes.

Siddhesh Poyarekar (8):
  Don't add access size hints to fortifiable functions
  Make sure that the fortified function conditionals are constant
  debug: Add tests for _FORTIFY_SOURCE=3
  __glibc_unsafe_len: Fix comment
  fortify: Fix spurious warning with realpath
  Enable _FORTIFY_SOURCE=3 for gcc 12 and above
  debug: Autogenerate _FORTIFY_SOURCE tests
  debug: Synchronize feature guards in fortified functions [BZ #28746]

 Makerules                           |   6 +
 debug/Makefile                      | 113 +++++++++-----
 debug/tst-chk2.c                    |   2 -
 debug/tst-chk3.c                    |   2 -
 debug/tst-chk4.cc                   |   1 -
 debug/tst-chk5.cc                   |   2 -
 debug/tst-chk6.cc                   |   2 -
 debug/{tst-chk1.c => tst-fortify.c} | 153 ++++++++++++-------
 debug/tst-lfschk1.c                 |   2 -
 debug/tst-lfschk2.c                 |   2 -
 debug/tst-lfschk3.c                 |   2 -
 debug/tst-lfschk4.cc                |   2 -
 debug/tst-lfschk5.cc                |   2 -
 debug/tst-lfschk6.cc                |   2 -
 debug/tst-realpath-chk.c            |  37 +++++
 include/features.h                  |   4 +-
 io/bits/poll2.h                     |  31 +---
 io/sys/poll.h                       |   6 +-
 libio/bits/stdio2.h                 | 110 ++++++--------
 libio/stdio.h                       |   4 +-
 misc/sys/cdefs.h                    |  60 +++++++-
 posix/bits/unistd.h                 | 176 +++++-----------------
 posix/unistd.h                      |  28 ++--
 socket/bits/socket2.h               |  34 ++---
 stdlib/bits/stdlib.h                |  57 +++----
 stdlib/stdlib.h                     |   5 +-
 string/bits/string_fortified.h      |  13 +-
 string/string.h                     |   2 +-
 support/xsignal.h                   |   2 +
 wcsmbs/bits/wchar2.h                | 221 ++++++++--------------------
 30 files changed, 498 insertions(+), 585 deletions(-)
 delete mode 100644 debug/tst-chk2.c
 delete mode 100644 debug/tst-chk3.c
 delete mode 100644 debug/tst-chk4.cc
 delete mode 100644 debug/tst-chk5.cc
 delete mode 100644 debug/tst-chk6.cc
 rename debug/{tst-chk1.c => tst-fortify.c} (90%)
 delete mode 100644 debug/tst-lfschk1.c
 delete mode 100644 debug/tst-lfschk2.c
 delete mode 100644 debug/tst-lfschk3.c
 delete mode 100644 debug/tst-lfschk4.cc
 delete mode 100644 debug/tst-lfschk5.cc
 delete mode 100644 debug/tst-lfschk6.cc
 create mode 100644 debug/tst-realpath-chk.c

-- 
2.35.1


             reply	other threads:[~2022-03-11 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 15:11 Siddhesh Poyarekar [this message]
2022-03-11 15:11 ` [committed 2.34 1/8] Don't add access size hints to fortifiable functions Siddhesh Poyarekar
2022-03-11 15:11 ` [committed 2.34 2/8] Make sure that the fortified function conditionals are constant Siddhesh Poyarekar
2022-03-11 15:11 ` [committed 2.34 3/8] debug: Add tests for _FORTIFY_SOURCE=3 Siddhesh Poyarekar
2022-03-11 15:11 ` [committed 2.34 4/8] __glibc_unsafe_len: Fix comment Siddhesh Poyarekar
2022-03-11 15:12 ` [committed 2.34 5/8] fortify: Fix spurious warning with realpath Siddhesh Poyarekar
2022-03-11 15:12 ` [committed 2.34 6/8] Enable _FORTIFY_SOURCE=3 for gcc 12 and above Siddhesh Poyarekar
2022-03-11 15:12 ` [committed 2.34 7/8] debug: Autogenerate _FORTIFY_SOURCE tests Siddhesh Poyarekar
2022-03-11 15:12 ` [committed 2.34 8/8] debug: Synchronize feature guards in fortified functions [BZ #28746] Siddhesh Poyarekar

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=20220311151203.3585163-1-siddhesh@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-stable@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).