From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@google.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Windsor <dave@nullcore.net>, Christoph Hellwig <hch@lst.de>
Subject: linux-next: build failure after merge of the kspp tree
Date: Wed, 8 Nov 2017 16:23:58 +1100 [thread overview]
Message-ID: <20171108162358.3a6d96bb@canb.auug.org.au> (raw)
Hi Kees,
After merging the kspp tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/linux/compiler_types.h:58:0,
from include/uapi/linux/stddef.h:2,
from include/linux/stddef.h:5,
from include/uapi/linux/posix_types.h:5,
from include/uapi/linux/types.h:14,
from include/linux/types.h:6,
from fs/xfs/xfs_linux.h:21,
from fs/xfs/xfs.h:35,
from fs/xfs/xfs_super.c:19:
fs/xfs/xfs_super.c: In function 'xfs_init_zones':
include/linux/compiler-gcc.h:166:2: error: 'xfs_ifork_t {aka struct xfs_ifork}' has no member named 'if_u2'
__builtin_offsetof(a, b)
^
include/linux/stddef.h:17:32: note: in expansion of macro '__compiler_offsetof'
#define offsetof(TYPE, MEMBER) __compiler_offsetof(TYPE, MEMBER)
^
fs/xfs/xfs_super.c:1862:4: note: in expansion of macro 'offsetof'
offsetof(xfs_inode_t, i_df.if_u2.if_inline_data),
^
In file included from include/uapi/linux/posix_types.h:5:0,
from include/uapi/linux/types.h:14,
from include/linux/types.h:6,
from fs/xfs/xfs_linux.h:21,
from fs/xfs/xfs.h:35,
from fs/xfs/xfs_super.c:19:
fs/xfs/xfs_super.c:1863:34: error: 'xfs_ifork_t {aka struct xfs_ifork}' has no member named 'if_u2'
sizeof_field(xfs_inode_t, i_df.if_u2.if_inline_data),
^
include/linux/stddef.h:22:66: note: in definition of macro 'sizeof_field'
#define sizeof_field(structure, field) sizeof((((structure *)0)->field))
^
Caused by commit
1d48144b9688 ("xfs: Define usercopy region in xfs_inode slab cache")
interacting with commit
43518812d297 ("xfs: remove support for inlining data/extents into the inode fork")
from the tree.
I just reverted the kspp tree commit as it seems like it is no longer
needed.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-11-08 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 5:23 Stephen Rothwell [this message]
2017-11-08 23:43 ` linux-next: build failure after merge of the kspp tree Kees Cook
2017-11-09 0:18 ` Darrick J. Wong
2017-11-09 0:31 ` Kees Cook
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=20171108162358.3a6d96bb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=dave@nullcore.net \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).