Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: linux-next: build failure after merge of the integrity tree
From:   Mimi Zohar <zohar@linux.ibm.com>
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        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>
Date:   Fri, 14 Jun 2019 10:09:07 -0400
In-Reply-To: <20190614153459.49c3d075@canb.auug.org.au>
References: <20190614153459.49c3d075@canb.auug.org.au>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <1560521347.4072.2.camel@linux.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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