linux-kernel - Re: Linux 5.8-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEJqkgi3w+zvMkRBP4VtAewX1UJxrVNRQ03MtRN_yH-PwOOScQ@mail.gmail.com>
Date:   Tue, 16 Jun 2020 22:11:46 +0200
From:   Gabriel C <nix.or.die@...glemail.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Hans de Goede <hdegoede@...hat.com>
Subject: Re: Linux 5.8-rc1

* Am So., 14. Juni 2020 um 22:44 Uhr schrieb Linus Torvalds
<torvalds@...ux-foundation.org>:

Hello,

> So I didn't really expect this, but 5.8 looks to be one of our biggest
> releases of all time.
>

I hit a compiler error caused by e4160b2e4b02377c67f8ecd05786811598f39acd.

x86/purgatory: Fail the build if purgatory.ro has missing symbols

Having CONFIG_STACKPROTECTOR* & CONFIG_KEXEC_FILE enabled always
results in a linking error like this:

LD      arch/x86/purgatory/purgatory.chk
ld: arch/x86/purgatory/purgatory.ro: in function `verify_sha256_digest':
purgatory.c:(.text+0x108): undefined reference to `__stack_chk_fail'
ld: arch/x86/purgatory/purgatory.ro: in function `sha256_transform':
sha256.c:(.text+0x1c74): undefined reference to `__stack_chk_fail'
ld: arch/x86/purgatory/purgatory.ro: in function `__sha256_final':
sha256.c:(.text+0x1e65): undefined reference to `__stack_chk_fail'
ld: arch/x86/purgatory/purgatory.ro: in function `_kstrtoull':
string.c:(.text+0x2107): undefined reference to `__stack_chk_fail'

I didn't look closer at that but from the error, it seems to be,
some missing -fstack-protector* vs -fno-stack-protector* checks
somewhere.


Best Regards,

Gabriel C