lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 14 Sep 2015 14:50:33 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Piotr Karbowski <piotr.karbowski@...il.com>,
	linux-kernel@...r.kernel.org, X86 ML <x86@...nel.org>,
	"K. Y. Srinivasan" <kys@...rosoft.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: Unable to link 4.3-rc1: undefined reference to
 `native_machine_crash_shutdown'

On 09/14/15 14:35, Piotr Karbowski wrote:
> Hello,
> 
> I wanted to try on the 4.3-rc1 kernel and it fails during linking with undefined reference to `native_machine_crash_shutdown'
> 
> # make
>   CHK     include/config/kernel.release
>   CHK     include/generated/uapi/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CHK     include/generated/bounds.h
>   CHK     include/generated/timeconst.h
>   CHK     include/generated/asm-offsets.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   CHK     kernel/config_data.h
>   LINK    vmlinux
>   LD      vmlinux.o
>   MODPOST vmlinux.o
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>     arch/x86/built-in.o: In function `hv_machine_crash_shutdown':
> mshyperv.c:(.text+0x7514c): undefined reference to `native_machine_crash_shutdown'
> Makefile:927: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
> 
> The dot config is as follow (stripped hashes and empty lines):
>  [deleted]

This has been happening for awhile now and has been reported several times.
Also there have been 2 or 3 patches posted to fix it... so what will it take
to get a fix merged?  anyone?

thnx,


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ