linux-kernel - Re: Stack protector kernel build error

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAGXu5jJ5CtgeQVYR-GLg-pGeQiOM66D4YxOystshBAa1XARcTg@mail.gmail.com>
Date:   Sat, 14 Oct 2017 20:42:45 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:     "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Stack protector kernel build error

On Sat, Oct 14, 2017 at 3:48 PM, Kees Cook <keescook@...omium.org> wrote:
> On Sat, Oct 14, 2017 at 3:45 PM, Kees Cook <keescook@...omium.org> wrote:
>> On Sat, Oct 14, 2017 at 12:53 PM, Robert Jarzmik <robert.jarzmik@...e.fr> wrote:
>>> Hi Kees,
>>>
>>> Today my linux-next build broke for the pxa architecture.
>>> My specific setup is :
>>>  - ARCH=arm make pxa_defconfig; ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make
>>>  - my compiler is:
>>>         rj@...garion:~/mio_linux/kernel$ arm-linux-gnueabi-gcc --version
>>>         arm-linux-gnueabi-gcc (Debian 6.3.0-18) 6.3.0 20170516
>>>
>>> And the error message is :
>>> rj@...garion:~/mio_linux/kernel$ make -j 4
>>>   CHK     include/config/kernel.release
>>> CONFIG_CC_STACKPROTECTOR_AUTO: Compiler does not support any known stack-protector
>>> Cannot use CONFIG_CC_STACKPROTECTOR_AUTO: not supported by compiler
>>> Makefile:1097: recipe for target 'prepare-compiler-check' failed
>>> make: *** [prepare-compiler-check] Error 1
>>> make: *** Waiting for unfinished jobs....
>>> make: *** wait: No child processes.  Stop.
>>>
>>>
>>> Is this expected, as I was under the impression my compiler was not that
>>> outdated ...
>>
>> Hmm, there's probably a bug in my attempt at making the ..._AUTO mode work.
>
> (Specifically, that report about compiler support should be a
> _warning_ not a _failure_ for _AUTO mode...)

Okay, I think I found it. Patch sent in separate email (to avoid
whitespace damage...)

-Kees

-- 
Kees Cook
Pixel Security