linux-kernel - Re: linux-next: build failure after merge of the integrity tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 14 Jun 2019 10:09:07 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Mimi Zohar <zohar@...ux.vnet.ibm.com>,
        Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Janne Karhunen <janne.karhunen@...il.com>
Subject: Re: linux-next: build failure after merge of the integrity tree

Hi Stephen,

On Fri, 2019-06-14 at 15:34 +1000, Stephen Rothwell wrote:
> 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.

Thank you!  A new version of the patch has been push to the next-
integrity branch.

Mimi