From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>, Matthew Garrett <mjg59@google.com>
Cc: kbuild-all@01.org,
linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [integrity:next-integrity-queued 22/22] security/integrity/evm/evm_crypto.c:93: undefined reference to `hash_algo_name'
Date: Fri, 15 Jun 2018 06:55:50 -0400 [thread overview]
Message-ID: <1529060150.3740.79.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <201806140958.6pTSK5nT%fengguang.wu@intel.com>
On Thu, 2018-06-14 at 09:07 +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity-queued
> head: 6497009f11c75bae55a3329dedcd3eeb8e282eaf
> commit: 6497009f11c75bae55a3329dedcd3eeb8e282eaf [22/22] evm: Allow non-SHA1 digital signatures
> config: x86_64-randconfig-ws0-06140615 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> git checkout 6497009f11c75bae55a3329dedcd3eeb8e282eaf
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
> security/integrity/evm/evm_crypto.o: In function `init_desc':
> >> security/integrity/evm/evm_crypto.c:93: undefined reference to `hash_algo_name'
>
> vim +93 security/integrity/evm/evm_crypto.c
Thanks! Removing the hash.h include should fix it. (commit updated.)
Mimi
next parent reply other threads:[~2018-06-15 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201806140958.6pTSK5nT%fengguang.wu@intel.com>
2018-06-15 10:55 ` Mimi Zohar [this message]
2018-06-15 15:20 ` [integrity:next-integrity-queued 22/22] security/integrity/evm/evm_crypto.c:93: undefined reference to `hash_algo_name' Mimi Zohar
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=1529060150.3740.79.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mjg59@google.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 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).