public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, Borislav Petkov <bp@alien8.de>
Cc: Adam Borowski <kilobyte@angband.pl>,
	Markus Trippelsdorf <markus@trippelsdorf.de>,
	Al Viro <viro@zeniv.linux.org.uk>,
	lkml <linux-kernel@vger.kernel.org>,
	npiggin@gmail.com
Subject: Re: 784d5699eddc ("x86: move exports to actual definitions")
Date: Thu, 20 Oct 2016 23:07:50 +0200	[thread overview]
Message-ID: <02ef0824-3208-7532-596c-043433a5f7c5@gmail.com> (raw)
In-Reply-To: <20161019094507.7c780449@gandalf.local.home>



On 19.10.2016 15:45, Steven Rostedt wrote:
> On Wed, 19 Oct 2016 12:23:25 +0200
> Borislav Petkov <bp@alien8.de> wrote:
> 
>> On Wed, Oct 19, 2016 at 02:10:04AM +0200, Adam Borowski wrote:
>>> Already being fixed, please take a look at the thread starting at
>>> 20161016002205.GA9686@vader; for your convenience I've put Nicholas Piggin's
>>> initial work, my lousy but works-for-me fix for x86, Arnd Bergmann's for arm
>>> at git@github.com:kilobyte/linux.git branch kbuild-exports.  
>>
>> Thanks.
>>
>> So you have three patches on that branch, I cherry-picked the first
>> two and it is almost fixed except the __fentry__ thing which is still
>> missing a CRC, see below.
>>
>> Adding Steve to CC too.
>>
>> WARNING: "__fentry__" [virt/lib/irqbypass.ko] has no CRC!
>> WARNING: "__fentry__" [sound/core/snd-hrtimer.ko] has no CRC!
>> WARNING: "__fentry__" [sound/core/seq/snd-seq.ko] has no CRC!
> 
> [ snip repeated failures of __fentry__ ]
> 
> Probably because of this:
> 
> #ifdef CC_USE_FENTRY
> # define function_hook __fentry__
> #else
> # define function_hook mcount
> #endif
> 
> [..]
> 
> Then you have this:
> 
> EXPORT_SYMBOL(function_hook)
> 
> which most likely exported the name "function_hook" and not
> "__fentry__".
> 
> Does this patch fix things for you? If it does, I can make it more
> generic (moving the MACRO_EXPORT_SYMBOL into the export.h header). And
> submit that.

kbuild-exports+your patch makes all my warning go away and *yay* that kernel
even boots to console .. ( X mode broken but this seems to be a different issue )


> -- Steve
> 
> diff --git a/arch/x86/kernel/mcount_64.S b/arch/x86/kernel/mcount_64.S
> index efe73aacf966..9420cd6c6dba 100644
> --- a/arch/x86/kernel/mcount_64.S
> +++ b/arch/x86/kernel/mcount_64.S
> @@ -295,7 +295,8 @@ trace:
>  	jmp fgraph_trace
>  END(function_hook)
>  #endif /* CONFIG_DYNAMIC_FTRACE */
> -EXPORT_SYMBOL(function_hook)
> +#define MACRO_EXPORT_SYMBOL(x) EXPORT_SYMBOL(x)
> +MACRO_EXPORT_SYMBOL(function_hook)
>  #endif /* CONFIG_FUNCTION_TRACER */
>  
>  #ifdef CONFIG_FUNCTION_GRAPH_TRACER
> 


Best Regards

      reply	other threads:[~2016-10-20 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 20:23 784d5699eddc ("x86: move exports to actual definitions") Borislav Petkov
2016-10-18 20:29 ` Markus Trippelsdorf
2016-10-18 20:40   ` Markus Trippelsdorf
2016-10-19  0:10   ` Adam Borowski
2016-10-19 10:23     ` Borislav Petkov
2016-10-19 13:45       ` Steven Rostedt
2016-10-20 21:07         ` Gabriel C [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=02ef0824-3208-7532-596c-043433a5f7c5@gmail.com \
    --to=nix.or.die@gmail.com \
    --cc=bp@alien8.de \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=npiggin@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=viro@zeniv.linux.org.uk \
    /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