All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Dingwall <james@dingwall.me.uk>
Cc: linux-kernel@vger.kernel.org, linux-stable@vger.kernel.org
Subject: Re: 4.4.11[01] build failure: undefined reference to `pvclock_pvti_cpu0_va'
Date: Wed, 10 Jan 2018 16:03:24 +0100	[thread overview]
Message-ID: <20180110150324.GA29193@kroah.com> (raw)
In-Reply-To: <20180110123252.GA208176@dingwall.me.uk>

On Wed, Jan 10, 2018 at 12:32:52PM +0000, James Dingwall wrote:
> On Fri, Jan 05, 2018 at 09:50:53PM +0000, James Dingwall wrote:
> > Hi,
> > 
> > I have just tried to build 4.4.110 but it failed with following message:
> > 
> > arch/x86/built-in.o: In function `map_vdso':
> > vma.c:(.text+0x8a3): undefined reference to `pvclock_pvti_cpu0_va'
> > make: *** [Makefile:953: vmlinux] Error 1
> > 
> > I found https://patchwork.kernel.org/patch/7906831/ which has a similar error and suggests that not enabling CONFIG_KVM_GUEST could be the cause, this is not set 
> > in my .config.  I suspect this commit from the patch could be the cause: 755bd549d9328d6d1e949a0a213f9a78e84d11fc.  Comparing arch/x86/include/asm/pvclock.h to 
> > 4.9.75 shows a different #ifdef condition:
> > 
> > 4.4:
> > 
> > #ifdef CONFIG_PARAVIRT_CLOCK
> > extern struct pvclock_vsyscall_time_info *pvclock_pvti_cpu0_va(void);
> > #else
> > static inline struct pvclock_vsyscall_time_info *pvclock_pvti_cpu0_va(void)
> > {
> >         return NULL;
> > }
> > #endif
> > 
> > 
> > 4.9:
> > 
> > #ifdef CONFIG_KVM_GUEST
> > extern struct pvclock_vsyscall_time_info *pvclock_pvti_cpu0_va(void);
> > #else
> > static inline struct pvclock_vsyscall_time_info *pvclock_pvti_cpu0_va(void)
> > {
> >         return NULL;
> > }
> > #endif
> > 
> > The #ifdef was changed by 8705d603edd49f1cff165cd3b7998f4c7f098d27 so perhaps that is required on the 4.4 stable branch?
> 
> My .config still fails with 4.4.111, 516fa79e77f7c4490ded10e7e1c36758482bde5a doesn't seem to be the fix.  
> cherry-picking 8705d603edd49f1cff165cd3b7998f4c7f098d27 makes the build work.

Thanks for letting me know, I've now queued that one up.

greg k-h

      reply	other threads:[~2018-01-10 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 21:50 4.4.110 build failure: undefined reference to `pvclock_pvti_cpu0_va' James Dingwall
2018-01-10 12:32 ` 4.4.11[01] " James Dingwall
2018-01-10 15:03   ` Greg Kroah-Hartman [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=20180110150324.GA29193@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=james@dingwall.me.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.