From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: Konstantin Meskhidze <konstantin.meskhidze@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the landlock tree
Date: Tue, 6 Jun 2023 13:02:36 +1000 [thread overview]
Message-ID: <20230606130236.4d339a46@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2728 bytes --]
Hi all,
After merging the landlock tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
security/landlock/net.c:165:51: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__lsm_ro_after_init'
165 | static struct security_hook_list landlock_hooks[] __lsm_ro_after_init = {
| ^~~~~~~~~~~~~~~~~~~
security/landlock/net.c: In function 'landlock_add_net_hooks':
security/landlock/net.c:172:28: error: 'landlock_hooks' undeclared (first use in this function)
172 | security_add_hooks(landlock_hooks, ARRAY_SIZE(landlock_hooks),
| ^~~~~~~~~~~~~~
security/landlock/net.c:172:28: note: each undeclared identifier is reported only once for each function it appears in
In file included from include/linux/container_of.h:5,
from include/linux/kernel.h:21,
from include/linux/uio.h:8,
from include/linux/socket.h:8,
from include/uapi/linux/in.h:25,
from include/linux/in.h:19,
from security/landlock/net.c:9:
include/linux/build_bug.h:16:51: error: bit-field '<anonymous>' width not an integer constant
16 | #define BUILD_BUG_ON_ZERO(e) ((int)(sizeof(struct { int:(-!!(e)); })))
| ^
include/linux/compiler.h:231:33: note: in expansion of macro 'BUILD_BUG_ON_ZERO'
231 | #define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0]))
| ^~~~~~~~~~~~~~~~~
include/linux/kernel.h:56:59: note: in expansion of macro '__must_be_array'
56 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
| ^~~~~~~~~~~~~~~
security/landlock/net.c:172:44: note: in expansion of macro 'ARRAY_SIZE'
172 | security_add_hooks(landlock_hooks, ARRAY_SIZE(landlock_hooks),
| ^~~~~~~~~~
security/landlock/net.c: At top level:
security/landlock/net.c:157:12: warning: 'hook_socket_connect' defined but not used [-Wunused-function]
157 | static int hook_socket_connect(struct socket *const sock,
| ^~~~~~~~~~~~~~~~~~~
security/landlock/net.c:150:12: warning: 'hook_socket_bind' defined but not used [-Wunused-function]
150 | static int hook_socket_bind(struct socket *const sock,
| ^~~~~~~~~~~~~~~~
Caused by commit
6d0bfdb25ce6 ("landlock: Add network rules and TCP hooks support")
I have use the landlock tree from next-20230605 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-06 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:02 Stephen Rothwell [this message]
2023-06-06 7:39 ` linux-next: build failure after merge of the landlock tree Mickaël Salaün
2023-10-27 5:34 Stephen Rothwell
[not found] ` <20231027.Soon0Gee4xul@digikod.net>
2023-10-28 15:34 ` Paul Moore
2023-11-05 23: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=20230606130236.4d339a46@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mic@digikod.net \
/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).