linux-kernel - linux-next: build failure after merge of the f2fs 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-next>] [day] [month] [year] [list]

Message-ID: <20201103123112.68f54d17@canb.auug.org.au>
Date:   Tue, 3 Nov 2020 12:31:12 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Jaegeuk Kim <jaegeuk@...nel.org>
Cc:     Daeho Jeong <daehojeong@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the f2fs tree

Hi all,

After merging the f2fs tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from <command-line>:32:
./usr/include/linux/f2fs.h:92:2: error: unknown type name 'u8'
   92 |  u8 algorithm;
      |  ^~
./usr/include/linux/f2fs.h:93:2: error: unknown type name 'u8'
   93 |  u8 log_cluster_size;
      |  ^~

Caused by commit

  63d18d4913e5 ("f2fs: add F2FS_IOC_GET_COMPRESS_OPTION ioctl")

You should only use the "__" versions of types in uapi headers.

I have used the version of the f2fs tree from next-20201102 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped