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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <10d92c2f-7120-18bb-1412-e3627d2d8f4c@suse.com>
Date:   Tue, 21 Apr 2020 09:33:56 +0800
From:   Qu Wenruo <wqu@...e.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
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



On 2020/4/21 上午9:13, Stephen Rothwell wrote:
> 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.

Any command to reproduce it?
As I want to avoid such problem in future development.

> 
>> 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.
> 
Thanks for the hint,
Qu



Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)