mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: Nadav Amit <namit@vmware.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Out of tree module build errors since v4.20-rc1
Date: Wed, 21 Nov 2018 16:14:47 -0500	[thread overview]
Message-ID: <20181121211447.weqjjk2fwbc27er6@oracle.com> (raw)
In-Reply-To: <5A24CA1A-3059-44BE-A0D5-4E29FC6E5BE9@vmware.com>

* Nadav Amit <namit@vmware.com> [181121 16:12]:
> > On Nov 21, 2018, at 12:56 PM, Liam R. Howlett <Liam.Howlett@Oracle.com> wrote:
> > 
> > 
> > My out of tree driver build is now reporting issues with the jump table:
> > 
> > ./include/linux/jump_label.h: In function ‘jump_entry_code’:
> > ./include/linux/jump_label.h:153:14: error: dereferencing pointer to incomplete type ‘const struct jump_entry’
> >  return entry->code;
> >              ^~
> > ./include/linux/jump_label.h: In function ‘jump_entry_set_init’:
> > ./include/linux/jump_label.h:180:7: error: dereferencing pointer to incomplete type ‘struct jump_entry’
> >  entry->key |= 2;
> >       ^~
> > ./include/linux/jump_label.h: At top level:
> > ./include/linux/jump_label.h:212:26: error: array type has incomplete element type ‘struct jump_entry’
> > extern struct jump_entry __start___jump_table[];
> >                          ^~~~~~~~~~~~~~~~~~~~
> > ./include/linux/jump_label.h:213:26: error: array type has incomplete element type ‘struct jump_entry’
> > extern struct jump_entry __stop___jump_table[];
> >                          ^~~~~~~~~~~~~~~~~~~
> > 
> > 
> > This happens in v4.20-rc3 as well, so I bisected between v4.19 to
> > v4.20-rc1 which resulted in the following commit:
> > 
> > b34006c4258c9c86597b6b7123d6a9a3513d6cd7 is the first bad commit
> > commit b34006c4258c9c86597b6b7123d6a9a3513d6cd7
> > Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Date:   Tue Sep 18 23:51:41 2018 -0700
> > 
> >    x86/jump_table: Use relative references
> > 
> > 
> > 
> > 
> > Initially I assumed this was my own fault, but my module does not have
> > these issues when using v4.19.  Is there anything I should try/change in
> > my module makefile, includes, etc to support this relative reference
> > code?
> 
> Do you see HAVE_ARCH_JUMP_LABEL_RELATIVE set in your kernel config?
> 

Yes:
 $ grep HAVE_ARCH_JUMP_LABEL_RELATIVE .config
 CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=y


I should have mentioned I ran 'make defoldconfig' between each bisect.

  reply	other threads:[~2018-11-21 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 20:56 Liam R. Howlett
2018-11-21 21:12 ` Nadav Amit
2018-11-21 21:14   ` Liam R. Howlett [this message]
2018-11-21 21:44     ` Ard Biesheuvel

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=20181121211447.weqjjk2fwbc27er6@oracle.com \
    --to=liam.howlett@oracle.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namit@vmware.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®