From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Qu Wenruo <wqu@suse.com>
Subject: linux-next: build failure after merge of the btrfs tree
Date: Tue, 21 Apr 2020 10:25:20 +1000 [thread overview]
Message-ID: <20200421102520.53623f09@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 5539 bytes --]
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:
./usr/include/linux/btrfs_tree.h:1127:2: error: unknown type name 'u8'
1127 | u8 tree_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1128:2: error: unknown type name 'u8'
1128 | u8 chunk_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1129:2: error: unknown type name 'u8'
1129 | u8 extent_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1130:2: error: unknown type name 'u8'
1130 | u8 fs_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1131:2: error: unknown type name 'u8'
1131 | u8 dev_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1132:2: error: unknown type name 'u8'
1132 | u8 csum_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1134:2: error: unknown type name 'u8'
1134 | u8 unused_8[10];
| ^~
./usr/include/linux/btrfs_tree.h:1148:2: error: unknown type name 'u8'
1148 | u8 csum[BTRFS_CSUM_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1150:2: error: unknown type name 'u8'
1150 | u8 fsid[BTRFS_FSID_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1177:2: error: unknown type name 'u8'
1177 | u8 root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1178:2: error: unknown type name 'u8'
1178 | u8 chunk_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1179:2: error: unknown type name 'u8'
1179 | u8 log_root_level;
| ^~
./usr/include/linux/btrfs_tree.h:1188:2: error: unknown type name 'u8'
1188 | u8 metadata_uuid[BTRFS_FSID_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1192:2: error: unknown type name 'u8'
1192 | u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1283:2: error: unknown type name 'u8'
1283 | u8 csum[BTRFS_CSUM_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1284:2: error: unknown type name 'u8'
1284 | u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */
| ^~
./usr/include/linux/btrfs_tree.h:1289:2: error: unknown type name 'u8'
1289 | u8 chunk_tree_uuid[BTRFS_UUID_SIZE];
| ^~
./usr/include/linux/btrfs_tree.h:1293:2: error: unknown type name 'u8'
1293 | u8 level;
| ^~
Caused by commit
8d80a063d508 ("btrfs: move on-disk structure definitions to btrfs_tree.h")
They should probably all be __u8 ...
I have applied the following patch for today.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 21 Apr 2020 10:19:20 +1000
Subject: [PATCH] btrfs: uapi headers should use __<type>
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
include/uapi/linux/btrfs_tree.h | 36 ++++++++++++++++-----------------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/include/uapi/linux/btrfs_tree.h b/include/uapi/linux/btrfs_tree.h
index a02318e4d2a9..1adf5971a966 100644
--- a/include/uapi/linux/btrfs_tree.h
+++ b/include/uapi/linux/btrfs_tree.h
@@ -1124,14 +1124,14 @@ struct btrfs_root_backup {
/* future */
__le64 unused_64[4];
- u8 tree_root_level;
- u8 chunk_root_level;
- u8 extent_root_level;
- u8 fs_root_level;
- u8 dev_root_level;
- u8 csum_root_level;
+ __u8 tree_root_level;
+ __u8 chunk_root_level;
+ __u8 extent_root_level;
+ __u8 fs_root_level;
+ __u8 dev_root_level;
+ __u8 csum_root_level;
/* future and to align */
- u8 unused_8[10];
+ __u8 unused_8[10];
} __attribute__ ((__packed__));
/*
@@ -1145,9 +1145,9 @@ struct btrfs_root_backup {
/* The super block basically lists the main trees of the FS. */
struct btrfs_super_block {
/* The first 4 fields must match struct btrfs_header */
- u8 csum[BTRFS_CSUM_SIZE];
+ __u8 csum[BTRFS_CSUM_SIZE];
/* FS specific UUID, visible to user */
- u8 fsid[BTRFS_FSID_SIZE];
+ __u8 fsid[BTRFS_FSID_SIZE];
__le64 bytenr; /* this block number */
__le64 flags;
@@ -1174,9 +1174,9 @@ struct btrfs_super_block {
__le64 compat_ro_flags;
__le64 incompat_flags;
__le16 csum_type;
- u8 root_level;
- u8 chunk_root_level;
- u8 log_root_level;
+ __u8 root_level;
+ __u8 chunk_root_level;
+ __u8 log_root_level;
struct btrfs_dev_item dev_item;
char label[BTRFS_LABEL_SIZE];
@@ -1185,11 +1185,11 @@ struct btrfs_super_block {
__le64 uuid_tree_generation;
/* The UUID written into btree blocks */
- u8 metadata_uuid[BTRFS_FSID_SIZE];
+ __u8 metadata_uuid[BTRFS_FSID_SIZE];
/* Future expansion */
__le64 reserved[28];
- u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
+ __u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
struct btrfs_root_backup super_roots[BTRFS_NUM_BACKUP_ROOTS];
} __attribute__ ((__packed__));
@@ -1280,17 +1280,17 @@ struct btrfs_super_block {
/* Every tree block (leaf or node) starts with this header. */
struct btrfs_header {
/* These first four must match the super block */
- u8 csum[BTRFS_CSUM_SIZE];
- u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */
+ __u8 csum[BTRFS_CSUM_SIZE];
+ __u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */
__le64 bytenr; /* Which block this node is supposed to live in */
__le64 flags;
/* Allowed to be different from the super from here on down. */
- u8 chunk_tree_uuid[BTRFS_UUID_SIZE];
+ __u8 chunk_tree_uuid[BTRFS_UUID_SIZE];
__le64 generation;
__le64 owner;
__le32 nritems;
- u8 level;
+ __u8 level;
} __attribute__ ((__packed__));
/*
--
2.25.1
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-21 0:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 0:25 Stephen Rothwell [this message]
2020-04-21 0:40 ` linux-next: build failure after merge of the btrfs tree Qu Wenruo
2020-04-21 1:13 ` Stephen Rothwell
2020-04-21 1:33 ` Qu Wenruo
2020-04-21 1:55 ` Stephen Rothwell
2020-04-22 21:29 ` David Sterba
2020-04-24 5:17 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2023-01-12 23:36 Stephen Rothwell
2023-01-13 10:59 ` David Sterba
2022-11-07 22:42 Stephen Rothwell
2022-11-08 11:21 ` David Sterba
2022-09-06 19:44 Stephen Rothwell
2022-08-21 23:44 Stephen Rothwell
2021-10-27 10:09 Stephen Rothwell
2021-10-29 8:28 ` Stephen Rothwell
2021-10-29 9:52 ` David Sterba
2021-10-29 10:50 ` David Sterba
[not found] ` <CAHp75VdXJEuY86pFC+bLoGbAYuGsA+KqEV-g4Dca25HHD-njHA@mail.gmail.com>
2021-10-29 12:14 ` David Sterba
2021-10-31 4:30 ` Stephen Rothwell
2021-10-08 4:03 Stephen Rothwell
2021-10-08 5:56 ` Qu Wenruo
2020-02-19 22:23 Stephen Rothwell
2020-02-21 11:30 ` David Sterba
2020-02-21 11:33 ` David Sterba
2015-08-21 0:42 Stephen Rothwell
2012-12-16 23:00 Stephen Rothwell
2012-12-17 0:15 ` Chris Mason
2012-12-17 2:52 ` Chris Mason
2012-12-17 3:13 ` Stephen Rothwell
2012-12-17 3:38 ` Chris Mason
2012-12-17 2:01 ` Chris Mason
2012-10-01 4:22 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200421102520.53623f09@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).