linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	kbuild-all@01.org
Subject: Re: [next:master 284/379] :undefined reference to `crypto_alloc_shash'
Date: Wed, 9 Jul 2014 08:30:28 -0400	[thread overview]
Message-ID: <20140709123028.GB26504@redhat.com> (raw)
In-Reply-To: <53bd23e5.Zuv44zZmJKnR/Dh5%fengguang.wu@intel.com>

On Wed, Jul 09, 2014 at 07:13:41PM +0800, kbuild test robot wrote:
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   35fcf5dd2a7d038c0fcbc161e353d73497350b86
> commit: ba0dc4038c9fec5fa2f94756065f02b8011f270b [284/379] 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':
> >> :(.text+0x4c808): undefined reference to `crypto_alloc_shash'
> >> :(.text+0x4c8d4): undefined reference to `crypto_shash_update'
> >> :(.text+0x4c918): undefined reference to `crypto_shash_update'
> >> :(.text+0x4c9f4): undefined reference to `crypto_shash_final'
> 

Hi,

This issue has been fixed by following patch.

http://ozlabs.org/~akpm/mmots/broken-out/kexec-load-and-relocate-purgatory-at-kernel-load-time-fix.patch

This should go away when above patch shows up in linux-next.

Thanks
Vivek

--
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>

      reply	other threads:[~2014-07-09 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 11:13 [next:master 284/379] :undefined reference to `crypto_alloc_shash' kbuild test robot
2014-07-09 12:30 ` Vivek Goyal [this message]

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=20140709123028.GB26504@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    /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).