From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 5/6] sunrpc: Suppress GCC -Os warning on user2netname
Date: Wed, 5 Oct 2022 09:52:37 -0400 [thread overview]
Message-ID: <Yz2MJXshGJsV6C0J@fedora> (raw)
In-Reply-To: <20220921135108.3324737-6-adhemerval.zanella@linaro.org>
On Wed, Sep 21, 2022 at 10:51:07AM -0300, Adhemerval Zanella via Libc-alpha wrote:
> GCC with -Os warns that sprint might overflow:
>
> netname.c: In function ‘user2netname’:
> netname.c:51:28: error: ‘%s’ directive writing up to 255 bytes into a
> region of size between 239 and 249 [-Werror=format-overflow=]
> 51 | sprintf (netname, "%s.%d@%s", OPSYS, uid, dfltdom);
> | ^~ ~~~~~~~
> netname.c:51:3: note: ‘sprintf’ output between 8 and 273 bytes into a
> destination of size 256
> 51 | sprintf (netname, "%s.%d@%s", OPSYS, uid, dfltdom);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> However the code does test prior the sprintf call that dfltdom plus
> the required extra space for OPSYS, uid, and extra character will not
> overflow and return 0 instead.
LGTM.
No regressions on x86_64.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>
> Checked on x86_64-linux-gnu and i686-linux-gnu.
> ---
> sunrpc/netname.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/sunrpc/netname.c b/sunrpc/netname.c
> index bf7f0b81c4..c1d1c43e50 100644
> --- a/sunrpc/netname.c
> +++ b/sunrpc/netname.c
> @@ -20,6 +20,7 @@
> #include <string.h>
> #include <rpc/rpc.h>
> #include <shlib-compat.h>
> +#include <libc-diag.h>
OK.
>
> #include "nsswitch.h"
>
> @@ -48,7 +49,12 @@ user2netname (char netname[MAXNETNAMELEN + 1], const uid_t uid,
> if ((strlen (dfltdom) + OPSYS_LEN + 3 + MAXIPRINT) > (size_t) MAXNETNAMELEN)
> return 0;
>
> + /* GCC with -Os warns that sprint might overflow while handling dfltdom,
> + however the above test does check if an overflow would happen. */
> + DIAG_PUSH_NEEDS_COMMENT;
> + DIAG_IGNORE_Os_NEEDS_COMMENT (8, "-Wformat-overflow");
> sprintf (netname, "%s.%d@%s", OPSYS, uid, dfltdom);
> + DIAG_POP_NEEDS_COMMENT;
OK. Agreed. The code above does that check.
> i = strlen (netname);
> if (netname[i - 1] == '.')
> netname[i - 1] = '\0';
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-10-05 13:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 13:51 [PATCH 0/6] Fix -Os build Adhemerval Zanella
2022-09-21 13:51 ` [PATCH 1/6] locale: prevent maybe-uninitialized errors with -Os [BZ #19444] Adhemerval Zanella
2022-10-05 13:39 ` Carlos O'Donell
2022-09-21 13:51 ` [PATCH 2/6] posix: Suppress -Os warnings on fnmatch Adhemerval Zanella
2022-10-05 13:47 ` Carlos O'Donell
2022-10-05 20:01 ` Paul Eggert
2022-09-21 13:51 ` [PATCH 3/6] posix: Suppress -Os may be used uninitialized warnings on regexec Adhemerval Zanella
2022-10-05 13:49 ` Carlos O'Donell
2022-09-21 13:51 ` [PATCH 4/6] rt: Initialize mq_send input on tst-mqueue{5,6} Adhemerval Zanella
2022-10-05 13:51 ` Carlos O'Donell
2022-09-21 13:51 ` [PATCH 5/6] sunrpc: Suppress GCC -Os warning on user2netname Adhemerval Zanella
2022-10-05 13:52 ` Carlos O'Donell [this message]
2022-09-21 13:51 ` [PATCH 6/6] x86: Fix -Os build (BZ #29576) Adhemerval Zanella
2022-10-05 14:10 ` Carlos O'Donell
2022-10-05 17:21 ` H.J. Lu
2022-10-05 17:38 ` Adhemerval Zanella Netto
2022-10-05 18:06 ` H.J. Lu
2022-10-05 20:43 ` Adhemerval Zanella Netto
2022-10-05 21:27 ` H.J. Lu
2022-10-05 13:40 ` [PATCH 0/6] Fix -Os build Carlos O'Donell
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=Yz2MJXshGJsV6C0J@fedora \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).