public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/release/2.34/master] __glibc_unsafe_len: Fix comment Date: Fri, 11 Mar 2022 15:12:14 +0000 (GMT) [thread overview] Message-ID: <20220311151214.3A2DD3857815@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=98ea9372cc8d60b12aa33e007fdd5f5fb042a651 commit 98ea9372cc8d60b12aa33e007fdd5f5fb042a651 Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Thu Dec 16 07:19:14 2021 +0530 __glibc_unsafe_len: Fix comment We know that the length is *unsafe*. Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org> (cherry picked from commit ae23fa3e5fe24daf94fc7f8e5268bb8ceeda7477) Diff: --- 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) \
reply other threads:[~2022-03-11 15:12 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=20220311151214.3A2DD3857815@sourceware.org \ --to=siddhesh@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: linkBe 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).