From: Ondrej Mosnacek <omosnace@redhat.com>
To: Petr Lautrbach <plautrba@redhat.com>
Cc: "selinux@vger.kernel.org" <selinux@vger.kernel.org>
Subject: Re: gcc 9.0.0 build issues
Date: Thu, 7 Feb 2019 16:32:39 +0100 [thread overview]
Message-ID: <CAFqZXNvBWzqs-kV5ES_He92kDvXUm0Re_3WzGiKoLBE_0dJVUg@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNt8Df0KX9qVmsGtxZroy6s1SFBt1Qmi5Psuv6z0+kTB7Q@mail.gmail.com>
On Fri, Feb 1, 2019 at 9:24 PM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> On Fri, Feb 1, 2019 at 8:36 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> > gcc-9.0.0-0.3.fc30.x86_64 from Fedora Rawhide:
> >
> > gcc version 9.0.0 20190119 (Red Hat 9.0.0-0.3) (GCC)
> >
> > $ make DESTDIR=~/obj install install-pywrap
> > ...
> >
> > make[2]: Entering directory
> > '/home/build/SELinuxProject-selinux/libsepol/src'
> > cc -O2 -Werror -Wall -Wextra -Wmissing-format-attribute
> > -Wmissing-noreturn -Wpointer-arith -Wshadow -Wstrict-prototypes
> > -Wundef -Wunused -Wwrite-strings -I. -I../include -D_GNU_SOURCE
> > -I../cil/include -fPIC -c -o genbools.o genbools.c
> > In function ‘strtrim’,
> > inlined from ‘process_boolean.constprop’ at genbools.c:52:2:
> > genbools.c:24:2: error: ‘strncpy’ output may be truncated copying
> > 8191 bytes from a string of length 8191
> > [-Werror=stringop-truncation]
> > 24 | strncpy(dest, ptr, size);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> >
>
> This is a typical strncpy() abuse. See 'man strncpy' -> /NOTES for how
> to handle the corner case correctly (same for similar issues below).
Actually, upon closer look it looks like there is no abuse and the
warning simply warns that only a part of the string might be copied
into the destination. I suppose we don't care about that possibility
here, so the best way to resolve the warning might be to just disable
the warning for this part of the code.
>
> > ...
> >
> > make[2]: Entering directory
> > '/home/build/SELinuxProject-selinux/libsepol/src'
> > cc -O2 -Werror -Wall -Wextra -Wmissing-format-attribute
> > -Wmissing-noreturn -Wpointer-arith -Wshadow -Wstrict-prototypes
> > -Wundef -Wunused -Wwrite-strings -I. -I../include -D_GNU_SOURCE
> > -I../cil/include -fPIC -DSHARED -c -o genbools.lo genbools.c
> > In function ‘strtrim’,
> > inlined from ‘process_boolean.constprop’ at genbools.c:52:2:
> > genbools.c:24:2: error: ‘strncpy’ output may be truncated copying
> > 8191 bytes from a string of length 8191
> > [-Werror=stringop-truncation]
> > 24 | strncpy(dest, ptr, size);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> >
> > ...
> >
> > make[2]: Entering directory
> > '/home/build/SELinuxProject-selinux/libselinux/src'
> > cc -O2 -Werror -Wall -Wextra -Wmissing-format-attribute
> > -Wmissing-noreturn -Wpointer-arith -Wshadow -Wstrict-prototypes
> > -Wundef -Wunused -Wwrite-strings -I../include -D_GNU_SOURCE
> > -DNO_ANDROID_BACKEND -c -o booleans.o booleans.c
> > In function ‘strtrim’,
> > inlined from ‘process_boolean’ at booleans.c:362:2:
> > booleans.c:335:2: error: ‘strncpy’ output may be truncated copying
> > between 8188 and 8191 bytes from a string of length 8191
> > [-Werror=stringop-truncation]
> > 335 | strncpy(dest, ptr, size);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> >
> > ...
> >
> >
> >
> > When libselinux is built separately, other CFLAGS is used:
> >
> > $ cd libselinux
> >
> > $ make DESTDIR=~/obj install install-pywrap
> > ...
> >
> > make[1]: Entering directory
> > '/home/build/SELinuxProject-selinux/libselinux/src'
> >
> > cc -O -Wall -W -Wundef -Wformat-y2k -Wformat-security -Winit-self
> > -Wmissing-include-dirs -Wunused -Wunknown-pragmas
> > -Wstrict-aliasing -Wshadow -Wpointer-arith -Wbad-function-cast
> > -Wcast-align -Wwrite-strings -Waggregate-return
> > -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes
> > -Wmissing-declarations -Wmissing-noreturn
> > -Wmissing-format-attribute -Wredundant-decls -Wnested-externs
> > -Winline -Winvalid-pch -Wvolatile-register-var
> > -Wdisabled-optimization -Wbuiltin-macro-redefined -Wattributes
> > -Wmultichar -Wdeprecated-declarations -Wdiv-by-zero
> > -Wdouble-promotion -Wendif-labels -Wextra -Wformat-extra-args
> > -Wformat-zero-length -Wformat=2 -Wmultichar -Woverflow
> > -Wpointer-to-int-cast -Wpragmas -Wno-missing-field-initializers
> > -Wno-sign-compare -Wno-format-nonliteral -Wframe-larger-than=32768
> > -fstack-protector-all --param=ssp-buffer-size=4 -fexceptions
> > -fasynchronous-unwind-tables -fdiagnostics-show-option
> > -funit-at-a-time -Werror -Wno-aggregate-return
> > -Wno-redundant-decls -fipa-pure-const -Wlogical-op
> > -Wpacked-bitfield-compat -Wsync-nand -Wcoverage-mismatch -Wcpp
> > -Wformat-contains-nul -Wnormalized=nfc -Wsuggest-attribute=const
> > -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure
> > -Wtrampolines -Wjump-misses-init -Wno-suggest-attribute=pure
> > -Wno-suggest-attribute=const -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
> > -Wstrict-overflow=5 -I../include -D_GNU_SOURCE
> > -DNO_ANDROID_BACKEND -c -o booleans.o booleans.c
> > booleans.c: In function ‘security_get_boolean_names’:
> > booleans.c:39:5: error: assuming signed overflow does not occur
> > when changing X +- C1 cmp C2 to X cmp C2 -+ C1
> > [-Werror=strict-overflow]
> > 39 | int security_get_boolean_names(char ***names, int *len)
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: all warnings being treated as errors
>
> This one is really weird... Perhaps a bug in GCC? At the very least
> the warning message and source code location are super confusing,
> which is a bug on its own...
>
> --
> Ondrej Mosnacek <omosnace at redhat dot com>
> Associate Software Engineer, Security Technologies
> Red Hat, Inc.
--
Ondrej Mosnacek <omosnace at redhat dot com>
Associate Software Engineer, Security Technologies
Red Hat, Inc.
prev parent reply other threads:[~2019-02-07 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 19:34 gcc 9.0.0 build issues Petr Lautrbach
2019-02-01 20:24 ` Ondrej Mosnacek
2019-02-07 12:40 ` Petr Lautrbach
2019-02-07 17:52 ` Roberts, William C
2019-02-07 18:17 ` Stephen Smalley
2019-02-07 18:18 ` Roberts, William C
2019-02-07 18:20 ` Stephen Smalley
2019-02-07 18:22 ` Roberts, William C
2019-02-08 19:40 ` Roberts, William C
2019-02-08 20:10 ` Ondrej Mosnacek
2019-02-12 16:37 ` Petr Lautrbach
2019-02-07 15:32 ` Ondrej Mosnacek [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=CAFqZXNvBWzqs-kV5ES_He92kDvXUm0Re_3WzGiKoLBE_0dJVUg@mail.gmail.com \
--to=omosnace@redhat.com \
--cc=plautrba@redhat.com \
--cc=selinux@vger.kernel.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 NNTP newsgroup(s).