[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2760877.KV1ZkH9Fsg@wuerfel>
Date: Wed, 01 Feb 2017 16:26:49 +0100
From: Arnd Bergmann <arnd@...db.de>
To: pageexec@...email.hu
Cc: Kees Cook <keescook@...omium.org>, Emese Revfy <re.emese@...il.com>, linux-kernel@...r.kernel.org, Josh Triplett <josh@...htriplett.org>, yamada.masahiro@...ionext.com, minipli@...linux.so, linux@...linux.org.uk, catalin.marinas@....com, linux@...musvillemoes.dk, david.brown@...aro.org, benh@...nel.crashing.org, tglx@...utronix.de, akpm@...ux-foundation.org, jlayton@...chiereds.net, sam@...nborg.org, kernel-hardening@...ts.openwall.com
Subject: Re: initify plugin crashes on arm allmodconfig
On Wednesday, February 1, 2017 4:10:03 PM CET PaX Team wrote:
> On 1 Feb 2017 at 14:52, Arnd Bergmann wrote:
>
> > On my ARM test builds (using a recent gcc-7 snapshot), allmodconfig failed with a compiler
> > crash, I have managed to minimize the test case to this:
> >
> > /home/arnd/cross-gcc/bin/arm-linux-gnueabi-gcc-7.0.1 -O2 -Wall -fplugin=/home/arnd/arm-soc/build/tmp/scripts/gcc-plugins/initify_plugin.so -DINITIFY_PLUGIN
> > -fplugin-arg-initify_plugin-search_init_exit_functions -fno-inline-functions-called-once -S atmel_lcdfb.i arm-linux-gnueabi-gcc-7.0.1: internal compiler error: Segmentation fault (program cc1)
> >
> [...]
> >
> > While trying to reproduce it, one time I ended up killing the gcc task when it
> > used more than 80 gigabytes (!) of memory after around six minutes of compiling
> > the same file (drivers/video/fbdev/atmel_lcdfb.c), but other times it just crashed
> > as above using various ARM cross compilers (4.9.3, 5.3, 6.1.1).
>
> i tried to reproduce it with 5.4 and 6.3 to no avail (arm64->arm cross compiler)
> so some more information will be needed. first, which plugin version did you try?
> second, if you build your own gcc, can you configure one with this additional
> option:
The plugin version is from today's next-20170201 version, and that is the
only version I've seen so far. Unfortunately I could not reproduce on
plain linux-next but only on my working tree, which contains countless
other patches.
I took some snapshots during the creduce run, the attached file is not fully
reduced but for me this version crashes on gcc-4.9.3, 5.3.1, 6.1.1, and 7.0.1.
I think the 4.9.3 build still had checks enabled, this is the output I get there:
arm-linux-gnueabi-gcc-4.9.3: internal compiler error: Segmentation fault (program cc1)
0x40c0c6 execute
/home/arnd/git/gcc/gcc/gcc.c:2854
0x40c464 do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:4658
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
0x40d16e do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5312
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
0x40d16e do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5312
0x40d0d3 do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5427
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
0x40d16e do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5312
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
0x40d16e do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5312
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
0x40d16e do_spec_1
/home/arnd/git/gcc/gcc/gcc.c:5312
0x40edc0 process_brace_body
/home/arnd/git/gcc/gcc/gcc.c:5941
0x40edc0 handle_braces
/home/arnd/git/gcc/gcc/gcc.c:5855
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
If you can't reproduce with the version below, I'll dig in further.
Arnd
View attachment "atmel_lcdfb.i.4" of type "text/plain" (15205 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
