linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warnings after merge of the ftrace tree
Date: Mon, 4 Jul 2016 15:42:07 +1000	[thread overview]
Message-ID: <20160704154207.159b102a@canb.auug.org.au> (raw)

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

             reply	other threads:[~2016-07-04  5:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04  5:42 Stephen Rothwell [this message]
2016-07-05 19:29 ` linux-next: build warnings after merge of the ftrace tree Steven Rostedt
2022-01-15  4:28 Stephen Rothwell
2022-01-15  9:55 ` Daniel Bristot de Oliveira
2023-01-30  5:51 Stephen Rothwell
2023-01-30 18:51 ` Steven Rostedt
2023-01-31  8:24   ` Bagas Sanjaya

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=20160704154207.159b102a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).