From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: Tree for Jul 30 [build failure on arm64]
Date: Fri, 31 Jul 2020 14:08:42 +1000 [thread overview]
Message-ID: <20200731140842.46abe589@canb.auug.org.au> (raw)
In-Reply-To: <72b073ba-ee41-1a1c-ce6c-ffd8b5936b09@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]
Hi all,
On Fri, 31 Jul 2020 10:46:52 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote:
>
> There's a build failure on arm64:
>
> In file included from ./include/linux/compat.h:17:0,
> from ./arch/arm64/include/asm/stat.h:13,
> from ./include/linux/stat.h:6,
> from ./include/linux/sysfs.h:22,
> from ./include/linux/kobject.h:20,
> from ./include/linux/of.h:17,
> from ./include/linux/irqdomain.h:35,
> from ./include/linux/acpi.h:13,
> from ./include/acpi/apei.h:9,
> from ./include/acpi/ghes.h:5,
> from ./include/linux/arm_sdei.h:8,
> from arch/arm64/kernel/asm-offsets.c:10:
> ./include/linux/fs.h: In function ‘vfs_whiteout’:
> ./include/linux/fs.h:1709:32: error: ‘S_IFCHR’ undeclared (first use in this function)
> return vfs_mknod(dir, dentry, S_IFCHR | WHITEOUT_MODE, WHITEOUT_DEV);
> ^
> ./include/linux/fs.h:1709:32: note: each undeclared identifier is reported only once for each
> function it appears in
> ./include/linux/fs.h: At top level:
> ./include/linux/fs.h:1855:46: warning: ‘struct kstat’ declared inside parameter list
> int (*getattr) (const struct path *, struct kstat *, u32, unsigned int);
> ^
> ./include/linux/fs.h:1855:46: warning: its scope is only this definition or declaration, which is
> probably not what you want
> ./include/linux/fs.h: In function ‘__mandatory_lock’:
> ./include/linux/fs.h:2325:25: error: ‘S_ISGID’ undeclared (first use in this function)
> return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID;
> ^
> ./include/linux/fs.h:2325:35: error: ‘S_IXGRP’ undeclared (first use in this function)
> return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID;
> ^
> ./include/linux/fs.h: In function ‘invalidate_remote_inode’:
> ./include/linux/fs.h:2588:6: error: implicit declaration of function ‘S_ISREG’
> [-Werror=implicit-function-declaration]
> if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
> ^
> ./include/linux/fs.h:2588:32: error: implicit declaration of function ‘S_ISDIR’
> [-Werror=implicit-function-declaration]
> if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
> ^
> ./include/linux/fs.h:2589:6: error: implicit declaration of function ‘S_ISLNK’
> [-Werror=implicit-function-declaration]
> S_ISLNK(inode->i_mode))
> ^
> ./include/linux/fs.h: In function ‘execute_ok’:
> ./include/linux/fs.h:2768:26: error: ‘S_IXUGO’ undeclared (first use in this function)
> return (inode->i_mode & S_IXUGO) || S_ISDIR(inode->i_mode);
Presumably caused by commit
b902bfb3f0e9 ("arm64: stop using <asm/compat.h> directly")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-31 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 11:46 linux-next: Tree for Jul 30 Stephen Rothwell
2020-07-30 15:07 ` linux-next: Tree for Jul 30 (drivers/crypto/chelsio/) Randy Dunlap
2020-07-31 2:46 ` linux-next: Tree for Jul 30 [build failure on arm64] Shaokun Zhang
2020-07-31 4:08 ` Stephen Rothwell [this message]
2020-07-31 8:30 ` Naresh Kamboju
2020-07-31 8:53 ` Stephen Rothwell
2020-07-31 9:00 ` Christoph Hellwig
2020-07-31 9:42 ` Stephen Rothwell
2020-07-31 8:56 ` Shaokun Zhang
2020-07-31 9:18 ` Christoph Hellwig
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=20200731140842.46abe589@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zhangshaokun@hisilicon.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).