From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-stable@sourceware.org
Cc: carlos@redhat.com, fweimer@redhat.com
Subject: [committed 2.34 4/8] __glibc_unsafe_len: Fix comment
Date: Fri, 11 Mar 2022 20:41:59 +0530 [thread overview]
Message-ID: <20220311151203.3585163-5-siddhesh@sourceware.org> (raw)
In-Reply-To: <20220311151203.3585163-1-siddhesh@sourceware.org>
We know that the length is *unsafe*.
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
(cherry picked from commit ae23fa3e5fe24daf94fc7f8e5268bb8ceeda7477)
---
misc/sys/cdefs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/misc/sys/cdefs.h b/misc/sys/cdefs.h
index 4825ff0351..3bb9f38916 100644
--- a/misc/sys/cdefs.h
+++ b/misc/sys/cdefs.h
@@ -168,7 +168,7 @@
__s, __osz)) \
&& __glibc_safe_len_cond ((__SIZE_TYPE__) (__l), __s, __osz))
-/* Conversely, we know at compile time that the length is safe if the
+/* Conversely, we know at compile time that the length is unsafe if the
__L * __S <= __OBJSZ condition can be folded to a constant and if it is
false. */
#define __glibc_unsafe_len(__l, __s, __osz) \
--
2.35.1
next prev parent 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 [committed 2.34 0/8] _FORTIFY_SOURCE=3 and fixes Siddhesh Poyarekar
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 ` Siddhesh Poyarekar [this message]
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-5-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).