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] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1908200042280.4008@nanos.tec.linutronix.de>
Date:   Tue, 20 Aug 2019 00:43:07 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     kbuild test robot <lkp@...el.com>
cc:     kbuild-all@...org, linux-kernel@...r.kernel.org, tipbuild@...or.com
Subject: Re: [tip:WIP.timers/core 49/68] include/linux/sched/types.h:16:2:
 error: unknown type name 'u64'

On Tue, 20 Aug 2019, Thomas Gleixner wrote:
> On Mon, 19 Aug 2019, Thomas Gleixner wrote:
> > On Tue, 20 Aug 2019, kbuild test robot wrote:
> > > 
> > > All errors (new ones prefixed by >>):
> > > 
> > >    In file included from <command-line>:0:0:
> > 
> > Huch? What kind of weird include chain is that?
> > 
> > > >> include/linux/sched/types.h:16:2: error: unknown type name 'u64'
> > >      u64    utime;
> > >      ^~~
> > >    include/linux/sched/types.h:17:2: error: unknown type name 'u64'
> > >      u64    stime;
> > >      ^~~
> > 
> > All (header) files which include that new header have u64 defined.
> 
> And building sparc64 allmodconfig does not expose this odd failure
> here. The build fails for a reason related to this series, but that's not
> caused by that sched/types.h header.

Now it came after fixing the other thing, but that build error is really
weird.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ