Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1436283 > unrolled thread

linux-next: build warnings after merge of the ftrace tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2016-07-04 07:50 +0200
Last post2016-07-05 21:30 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  linux-next: build warnings after merge of the ftrace tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-07-04 07:50 +0200
    Re: linux-next: build warnings after merge of the ftrace tree Steven Rostedt <rostedt@goodmis.org> - 2016-07-05 21:30 +0200

#1436283 — linux-next: build warnings after merge of the ftrace tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-07-04 07:50 +0200
Subjectlinux-next: build warnings after merge of the ftrace tree
Message-ID<rR4Vz-1HH-5@gated-at.bofh.it>
Hi Steven,

After merging the ftrace tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:

WARNING: kernel/trace/libftrace.o(.text+0x9569): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x9577): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x9582): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x958d): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x9598): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x95a3): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/libftrace.o(.text+0x95ae): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:ftrace_filter_param
The function ftrace_init_tracefs() references
the variable __initdata ftrace_filter_param.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of ftrace_filter_param is wrong.

WARNING: kernel/trace/built-in.o(.text+0x9789): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/built-in.o(.text+0x9797): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/built-in.o(.text+0x97a2): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/trace/built-in.o(.text+0x97ad): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/built-in.o(.text+0x97b8): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/built-in.o(.text+0x97c3): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/trace/built-in.o(.text+0x97ce): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:ftrace_filter_param
The function ftrace_init_tracefs() references
the variable __initdata ftrace_filter_param.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of ftrace_filter_param is wrong.

WARNING: kernel/built-in.o(.text+0x18bbb9): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/built-in.o(.text+0x18bbc7): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/built-in.o(.text+0x18bbd2): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: kernel/built-in.o(.text+0x18bbdd): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/built-in.o(.text+0x18bbe8): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/built-in.o(.text+0x18bbf3): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: kernel/built-in.o(.text+0x18bbfe): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:ftrace_filter_param
The function ftrace_init_tracefs() references
the variable __initdata ftrace_filter_param.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of ftrace_filter_param is wrong.

WARNING: vmlinux.o(.text+0x2636f9): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: vmlinux.o(.text+0x263707): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: vmlinux.o(.text+0x263712): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:function_stats
The function ftrace_init_tracefs() references
the variable __initdata function_stats.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of function_stats is wrong.

WARNING: vmlinux.o(.text+0x26371d): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: vmlinux.o(.text+0x263728): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: vmlinux.o(.text+0x263733): Section mismatch in reference from the function ftrace_init_tracefs() to the (unknown reference) .init.data:(unknown)
The function ftrace_init_tracefs() references
the (unknown reference) __initdata (unknown).
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of (unknown) is wrong.

WARNING: vmlinux.o(.text+0x26373e): Section mismatch in reference from the function ftrace_init_tracefs() to the variable .init.data:ftrace_filter_param
The function ftrace_init_tracefs() references
the variable __initdata ftrace_filter_param.
This is often because ftrace_init_tracefs lacks a __initdata 
annotation or the annotation of ftrace_filter_param is wrong.

Introduced (I assume) by commit

  345ddcc882d8 ("ftrace: Have set_ftrace_pid use the bitmap like events do")

-- 
Cheers,
Stephen Rothwell

[toc] | [next] | [standalone]


#1437238

FromSteven Rostedt <rostedt@goodmis.org>
Date2016-07-05 21:30 +0200
Message-ID<rREcF-73g-9@gated-at.bofh.it>
In reply to#1436283
On Mon, 4 Jul 2016 15:42:07 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Steven,
> 
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:

I'm currently running the patch I posted previously and if all goes
well will have that patch added to my ftrace-next repo tonight.
Fengguang Wu's bot caught this, but I was working on something else.
Over the weekend I was wondering why I haven't pushed my repo yet (I
forgot about this), and pushed my branch.

So this doesn't happen again, I added:

 # CONFIG_SECTION_MISMATCH_WARN_ONLY is not set

to one of the configs I use for testing, as my tests didn't die when
a mismatch was added and caught.

-- Steve

Link: http://lkml.kernel.org/r/20160704102139.19cbc0d9@gandalf.local.home

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web