linux-kernel - Re: next: s390 allyesconfig fails to compile samples/seccomp

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]

Date:   Fri, 6 Jan 2017 12:18:42 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: next: s390 allyesconfig fails to compile samples/seccomp

On Fri, Jan 6, 2017 at 7:04 AM, Michal Hocko <mhocko@...nel.org> wrote:
> Hi,
> I am not relly sure what went wrong, but I've noticed that allyesconfig
> doesn't compile with my s390 crosscompiler with a strange error
> messages for linux-next (next-20170106). Linus' tree compiles just fine.
> It smells like some headers include problems because
> $ git diff origin/master..next/master -- samples/seccomp/
> doesn't show anything...

Oh, how strange. Did __BITS_PER_LONG move around? That's part of uapi...


>
> samples/seccomp/bpf-helper.h:134:2: error: #error __BITS_PER_LONG value unusable.
>  #error __BITS_PER_LONG value unusable.
>   ^

#include <asm/bitsperlong.h>    /* for __BITS_PER_LONG */

Hm, maybe this should be uapi/asm/bitsperlong.h ?

Let me see if I can reproduce this...

-Kees

-- 
Kees Cook
Nexus Security