linux-kernel - Re: [PATCH 1/2] x86, Kconfig: Move PARAVIRT

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130125085146.GA23404@pd.tnic>
Date:	Fri, 25 Jan 2013 09:51:47 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	jasowang@...hat.com, Thomas Gleixner <tglx@...utronix.de>,
	JBeulich@...e.com, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH 1/2] x86, Kconfig: Move PARAVIRT_DEBUG into the paravirt
 menu

On Fri, Jan 25, 2013 at 09:21:26AM +0100, Ingo Molnar wrote:
> 
> So, these two patches, on top of -tip, produce:
> 
> vmw_balloon.c:(.init.text+0x8506): undefined reference to `x86_hyper'
> vmw_balloon.c:(.init.text+0x850a): undefined reference to `x86_hyper_vmware'

Hmm, I somehow can't trigger it here. And the thing is, vmw_balloon.c is
built only when CONFIG_VMWARE_BALLOON is set and that is not the case in
this config.

[ … ]

> CONFIG_HMC6352=y
> # CONFIG_DS1682 is not set
> # CONFIG_VMWARE_BALLOON is not set

But still, I can see how this can still trigger because code is assuming
the presence of x86_hyper which those patches don't guarantee anymore. I
still haven't sorted out through my test builds here, will do so now and
check.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/