[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+rn+69QiLR=Rbd6ys7atL8Z8THyazW_T3Z=CAw0n8xzg@mail.gmail.com>
Date: Mon, 9 Jul 2018 11:06:02 -0700
From: Kees Cook <keescook@...omium.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: LKML <linux-kernel@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
linux-s390 <linux-s390@...r.kernel.org>
Subject: Re: Build/qemu test results for v4.18-rc4
On Mon, Jul 9, 2018 at 10:55 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> s390:allmodconfig:
>
> arch/s390/kernel/als.o: In function `verify_facilities':
> als.c:(.init.text+0x24): undefined reference to `latent_entropy'
> als.c:(.init.text+0xae): undefined reference to `latent_entropy'
> make[3]: *** [arch/s390/boot/compressed/vmlinux] Error 1
> make[2]: *** [arch/s390/boot/compressed/vmlinux] Error 2
> make[1]: *** [bzImage] Error 2
>
> This problem is only seen when using a compiler which has the relevant
> plugins enabled. Bisect points to commit 1658dcee3d43ed ("gcc-plugins:
> allow to enable GCC_PLUGINS for COMPILE_TEST") as the culprit. I don't
> know if a fix for v4.18 has been submitted. The s390 boot code in -next
> has been rearranged and the problem is no longer seen there.
Hm, that would imply that mm/page_alloc.o wasn't visible during the
als.o linking? But ... if the problem is gone, I guess... good?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists