linux-kernel - Re: linux-next: build failure after merge of the btrfs tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200421111324.2148fe05@canb.auug.org.au>
Date:   Tue, 21 Apr 2020 11:13:24 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Qu Wenruo <wqu@...e.com>
Cc:     David Sterba <dsterba@...e.cz>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs tree

Hi Qu,

On Tue, 21 Apr 2020 08:40:45 +0800 Qu Wenruo <wqu@...e.com> wrote:
>
> On 2020/4/21 上午8:25, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the btrfs tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > In file included from <command-line>:32:  
> 
> Any extra info?

That is a build test of the uapi headers to make syre that they are
self contained.

> It builds fine in my environment, with older HEAD though.
> 
> Is there any new commits which changed <linux/types.h> header?
> As it should includes u8 typedef.

My understanding is that you should only use the __ versions of the
kernel types in uapi headers to avoid namespace contamination.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped