public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/28989] __snprintf_chk bounds check is too strict
Date: Thu, 24 Mar 2022 07:01:04 +0000	[thread overview]
Message-ID: <bug-28989-131-McNm3gtJi0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28989-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28989

--- Comment #5 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
(In reply to dj@redhat.com from comment #4)
> *** possible buffer overflow detected - length exceeds buffer ***

Strictly speaking, I agree that the message is misleading, but I'm not sure if
changing it is worthwhile.  If we agree to change it then we should probably do
the same for strncpy, wcsncpy, vsnprintf, etc. too since they all use the same
check to fail on overflow.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-03-24  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 14:29 [Bug stdio/28989] New: " siddhesh at sourceware dot org
2022-03-22 14:30 ` [Bug stdio/28989] " siddhesh at sourceware dot org
2022-03-22 14:47 ` schwab@linux-m68k.org
2022-03-22 14:50 ` siddhesh at sourceware dot org
2022-03-22 15:16 ` carlos at redhat dot com
2022-03-22 18:21 ` dj at redhat dot com
2022-03-23  8:48 ` mliska at suse dot cz
2022-03-24  7:01 ` siddhesh at sourceware dot org [this message]
2024-01-17 19:47 ` i at maskray dot me
2024-01-18  4:58 ` sam at gentoo dot org
2024-01-26  1:50 ` gabravier at gmail dot com

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=bug-28989-131-McNm3gtJi0@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).