From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild-all@01.org
Subject: Re: [next:master 284/380] cpu_pm.c:undefined reference to `crypto_alloc_shash'
Date: Mon, 7 Jul 2014 12:04:14 -0700 [thread overview]
Message-ID: <20140707120414.2cb6c1da2b71a91c24ced4aa@linux-foundation.org> (raw)
In-Reply-To: <53b516e4.rgxkJyIm0d6ktGNY%fengguang.wu@intel.com>
On Thu, 03 Jul 2014 16:40:04 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 0e9ce823ad7bc6b85c279223ae6638d47089461e
> commit: ba0dc4038c9fec5fa2f94756065f02b8011f270b [284/380] kexec: load and relocate purgatory at kernel load time
> config: make ARCH=arm nuc950_defconfig
>
> All error/warnings:
>
> kernel/built-in.o: In function `sys_kexec_file_load':
> >> cpu_pm.c:(.text+0x4a580): undefined reference to `crypto_alloc_shash'
> >> cpu_pm.c:(.text+0x4a654): undefined reference to `crypto_shash_update'
> >> cpu_pm.c:(.text+0x4a698): undefined reference to `crypto_shash_update'
> >> cpu_pm.c:(.text+0x4a778): undefined reference to `crypto_shash_final'
yup, kexec now requires crypto but the patch only fixes x86's Kconfig.
Was selecting crypto the correct decision? Is there no case for using
kexec without this signing capability?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-07-07 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 8:40 [next:master 284/380] cpu_pm.c:undefined reference to `crypto_alloc_shash' kbuild test robot
2014-07-07 19:04 ` Andrew Morton [this message]
2014-07-08 20:27 ` Vivek Goyal
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=20140707120414.2cb6c1da2b71a91c24ced4aa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=vgoyal@redhat.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).