All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: linux-next: build failure after merge of the integrity tree
Date: Fri, 14 Jun 2019 10:09:07 -0400	[thread overview]
Message-ID: <1560521347.4072.2.camel@linux.ibm.com> (raw)
In-Reply-To: <20190614153459.49c3d075@canb.auug.org.au>

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


  reply	other threads:[~2019-06-14 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  5:34 linux-next: build failure after merge of the integrity tree Stephen Rothwell
2019-06-14 14:09 ` Mimi Zohar [this message]
  -- 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=1560521347.4072.2.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=janne.karhunen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zohar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.