From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mimi Zohar <zohar@linux•vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Janne Karhunen <janne.karhunen@gmail•com>
Subject: linux-next: build failure after merge of the integrity tree
Date: Fri, 14 Jun 2019 15:34:59 +1000 [thread overview]
Message-ID: <20190614153459.49c3d075@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Hi all,
After merging the integrity tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/infiniband/core/device.c: In function 'ib_core_init':
drivers/infiniband/core/device.c:2531:8: error: implicit declaration of function 'register_blocking_lsm_notifier'; did you mean 'register_lsm_notifier'? [-Werror=implicit-function-declaration]
ret = register_blocking_lsm_notifier(&ibdev_lsm_nb);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
register_lsm_notifier
drivers/infiniband/core/device.c:2550:2: error: implicit declaration of function 'unregister_blocking_lsm_notifier'; did you mean 'unregister_lsm_notifier'? [-Werror=implicit-function-declaration]
unregister_blocking_lsm_notifier(&ibdev_lsm_nb);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
unregister_lsm_notifier
Caused by commit
bafe78e69508 ("LSM: switch to blocking policy update notifiers")
CONFIG_SECURITY is not set for this build and the !CONFIG_SECURITY
declarations were not fixed up in linux/security.h.
I have used the integrity tree from next-20190613 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-06-14 5:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 5:34 Stephen Rothwell [this message]
2019-06-14 14:09 ` linux-next: build failure after merge of the integrity tree Mimi Zohar
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 0:51 Stephen Rothwell
2023-02-07 12:48 ` Roberto Sassu
2019-08-06 2:15 Stephen Rothwell
2019-08-06 3:18 ` Thiago Jung Bauermann
2019-08-06 3:45 ` Stephen Rothwell
2019-08-06 19:02 ` Mimi Zohar
2018-07-17 4:40 Stephen Rothwell
2018-07-17 13:18 ` Mimi Zohar
2018-07-17 22:21 ` 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=20190614153459.49c3d075@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.kasatkin@gmail$(echo .)com \
--cc=janne.karhunen@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=zohar@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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