From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: linux-kernel@vger.kernel.org
Subject: linux-next 20220125 - build failure in objtool with gcc 12
Date: Wed, 26 Jan 2022 17:56:54 -0500 [thread overview]
Message-ID: <20494.1643237814@turing-police> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Fedora Rawhide shipped gcc12, which apparently includes a new warning that
causes a build failure. Apparently, it's unable to figure out that 'ptr' remains
valid on failed realloc(), and we only call realloc() again on failures...
CC /usr/src/linux-next/tools/objtool/exec-cmd.o
CC /usr/src/linux-next/tools/objtool/help.o
In file included from help.c:12:
In function 'xrealloc',
inlined from 'add_cmdname' at help.c:24:2:
subcmd-util.h:56:23: error: pointer may be used after 'realloc' [-Werror=use-after-free]
56 | ret = realloc(ptr, size);
| ^~~~~~~~~~~~~~~~~~
subcmd-util.h:52:21: note: call to 'realloc' here
52 | void *ret = realloc(ptr, size);
| ^~~~~~~~~~~~~~~~~~
subcmd-util.h:58:31: error: pointer may be used after 'realloc' [-Werror=use-after-free]
58 | ret = realloc(ptr, 1);
| ^~~~~~~~~~~~~~~
subcmd-util.h:52:21: note: call to 'realloc' here
52 | void *ret = realloc(ptr, size);
| ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[4]: *** [/usr/src/linux-next/tools/build/Makefile.build:97: /usr/src/linux-next/tools/objtool/help.o] Error 1
make[3]: *** [Makefile:59: /usr/src/linux-next/tools/objtool/libsubcmd-in.o] Error 2
make[2]: *** [Makefile:63: /usr/src/linux-next/tools/objtool/libsubcmd.a] Error 2
make[1]: *** [Makefile:69: objtool] Error 2
make: *** [Makefile:1405: tools/objtool] Error 2
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next reply other threads:[~2022-01-26 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:56 Valdis Klētnieks [this message]
2022-01-27 15:34 ` linux-next 20220125 - build failure in objtool with gcc 12 Justin Forbes
2022-02-12 17:50 ` Kees Cook
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=20494.1643237814@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.