linux-kernel - Re: randconfig build error with next-20151215, in arch/x86/entry/vdso/vma.c

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] [day] [month] [year] [list]

Date:	Tue, 15 Dec 2015 08:42:09 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Jim Davis <jim.epost@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	tglx <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
	hpa <hpa@...or.com>, x86 <x86@...nel.org>
Subject: Re: randconfig build error with next-20151215, in arch/x86/entry/vdso/vma.c

On Tue, Dec 15, 2015 at 8:32 AM, Jim Davis <jim.epost@...il.com> wrote:
> Building with the attached random configuration file,
>
> arch/x86/built-in.o: In function `map_vdso':
> vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va'

Whoops, thanks!  I confused CONFIG_PARAVIRT_CLOCK and CONFIG_KVM_GUEST.

Ingo, what should I do?  AFAICS these aren't currently in -tip or
queued for -next at all.  Should I send a fixup on top of the pending
patches?  Should I resend both series, with this problem fixed, merged
into one bigger series?

--Andy

>
>
> --
> Jim



-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/