From: Florian Weimer <fweimer@redhat.com>
To: Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>
Cc: Stefan Liebler <stli@linux.ibm.com>
Subject: Re: Question regarding gcc 12 Werror=stringop-overflow in iconv/loop.c
Date: Wed, 27 Apr 2022 17:24:21 +0200 [thread overview]
Message-ID: <87y1zqft22.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <7f96a24c-86c7-1fb9-7820-1e27bce6cd56@linux.ibm.com> (Stefan Liebler via Libc-alpha's message of "Wed, 27 Apr 2022 16:55:01 +0200")
* Stefan Liebler via Libc-alpha:
> Is there a guarantee that (inptr < inend) is always met?
When calling iconv (the external API), inptr <= inend must hold (no
pointer wraparound). I think there is a minimum-input-size check in
iconv/loop.c, so it follows that we have inptr < inend. I think.
Thanks,
Florian
prev parent reply other threads:[~2022-04-27 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 14:55 Stefan Liebler
2022-04-27 15:24 ` Florian Weimer [this message]
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=87y1zqft22.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.com \
/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).