WARNING: arch/x86/kernel/built-in.o(.text+0x11b41): Section mismatch
in reference from the variable ftrace_test_p6nop to the function
.init.text:ftrace_dyn_arch_init()
The function ftrace_test_p6nop() references
the function __init ftrace_dyn_arch_init().
This is often because ftrace_test_p6nop lacks a __init
annotation or the annotation of ftrace_dyn_arch_init is wrong.
WARNING: arch/x86/kernel/built-in.o(.text+0x11b4b): Section mismatch
in reference from the variable ftrace_test_nop5 to the function
.init.text:ftrace_dyn_arch_init()
The function ftrace_test_nop5() references
the function __init ftrace_dyn_arch_init().
This is often because ftrace_test_nop5 lacks a __init
annotation or the annotation of ftrace_dyn_arch_init is wrong.
This patch fixes the above warnings. Introduced by
'linux-next.patch'(2.6.27-rc5-mm1-broken-out).
Thanks.
Signed-off-by: Md.Rakib H. Mullick([email protected])
--- linux-2.6-mm.orig/arch/x86/kernel/ftrace.c 2008-10-11
18:55:52.000000000 +0600
+++ linux-2.6-mm/arch/x86/kernel/ftrace.c 2008-10-12 18:59:38.000000000 +0600
@@ -105,7 +105,7 @@ notrace int ftrace_mcount_set(unsigned l
return 0;
}
-int __init ftrace_dyn_arch_init(void *data)
+int ftrace_dyn_arch_init(void *data)
{
extern const unsigned char ftrace_test_p6nop[];
extern const unsigned char ftrace_test_nop5[];
* Rakib Mullick <[email protected]> wrote:
> WARNING: arch/x86/kernel/built-in.o(.text+0x11b41): Section mismatch
> in reference from the variable ftrace_test_p6nop to the function
> .init.text:ftrace_dyn_arch_init()
> The function ftrace_test_p6nop() references
> the function __init ftrace_dyn_arch_init().
> This is often because ftrace_test_p6nop lacks a __init
> annotation or the annotation of ftrace_dyn_arch_init is wrong.
>
> WARNING: arch/x86/kernel/built-in.o(.text+0x11b4b): Section mismatch
> in reference from the variable ftrace_test_nop5 to the function
> .init.text:ftrace_dyn_arch_init()
> The function ftrace_test_nop5() references
> the function __init ftrace_dyn_arch_init().
> This is often because ftrace_test_nop5 lacks a __init
> annotation or the annotation of ftrace_dyn_arch_init is wrong.
>
> This patch fixes the above warnings. Introduced by
> 'linux-next.patch'(2.6.27-rc5-mm1-broken-out).
> Thanks.
>
> Signed-off-by: Md.Rakib H. Mullick([email protected])
applied to tip/tracing/urgent, thanks!
Ingo
* Ingo Molnar <[email protected]> wrote:
>
> * Rakib Mullick <[email protected]> wrote:
>
> > WARNING: arch/x86/kernel/built-in.o(.text+0x11b41): Section mismatch
> > in reference from the variable ftrace_test_p6nop to the function
> > .init.text:ftrace_dyn_arch_init()
> > The function ftrace_test_p6nop() references
> > the function __init ftrace_dyn_arch_init().
> > This is often because ftrace_test_p6nop lacks a __init
> > annotation or the annotation of ftrace_dyn_arch_init is wrong.
> >
> > WARNING: arch/x86/kernel/built-in.o(.text+0x11b4b): Section mismatch
> > in reference from the variable ftrace_test_nop5 to the function
> > .init.text:ftrace_dyn_arch_init()
> > The function ftrace_test_nop5() references
> > the function __init ftrace_dyn_arch_init().
> > This is often because ftrace_test_nop5 lacks a __init
> > annotation or the annotation of ftrace_dyn_arch_init is wrong.
> >
> > This patch fixes the above warnings. Introduced by
> > 'linux-next.patch'(2.6.27-rc5-mm1-broken-out).
> > Thanks.
> >
> > Signed-off-by: Md.Rakib H. Mullick([email protected])
>
> applied to tip/tracing/urgent, thanks!
actually, this patch is wrong: the problem highlighted in that warning
is that ftrace_test_p6nop is non-__init while ftrace_dyn_arch_init() is
__init. So the proper solution is to mark ftrace_test_p6nop init as
well. (it's an assembly label so thus slightly more complex than usual,
but doable.)
Ingo
On 10/22/08, Ingo Molnar <[email protected]> wrote:
>
> * Ingo Molnar <[email protected]> wrote:
>
>>
>> * Rakib Mullick <[email protected]> wrote:
>>
>> > WARNING: arch/x86/kernel/built-in.o(.text+0x11b41): Section mismatch
>> > in reference from the variable ftrace_test_p6nop to the function
>> > .init.text:ftrace_dyn_arch_init()
>> > The function ftrace_test_p6nop() references
>> > the function __init ftrace_dyn_arch_init().
>> > This is often because ftrace_test_p6nop lacks a __init
>> > annotation or the annotation of ftrace_dyn_arch_init is wrong.
>> >
>> > WARNING: arch/x86/kernel/built-in.o(.text+0x11b4b): Section mismatch
>> > in reference from the variable ftrace_test_nop5 to the function
>> > .init.text:ftrace_dyn_arch_init()
>> > The function ftrace_test_nop5() references
>> > the function __init ftrace_dyn_arch_init().
>> > This is often because ftrace_test_nop5 lacks a __init
>> > annotation or the annotation of ftrace_dyn_arch_init is wrong.
>> >
>> > This patch fixes the above warnings. Introduced by
>> > 'linux-next.patch'(2.6.27-rc5-mm1-broken-out).
>> > Thanks.
>> >
>> > Signed-off-by: Md.Rakib H. Mullick([email protected])
>>
>> applied to tip/tracing/urgent, thanks!
>
> actually, this patch is wrong: the problem highlighted in that warning
> is that ftrace_test_p6nop is non-__init while ftrace_dyn_arch_init() is
> __init. So the proper solution is to mark ftrace_test_p6nop init as
> well. (it's an assembly label so thus slightly more complex than usual,
> but doable.)
Does the following solves the problem?
Thanks.
--- linux-2.6-orig/arch/x86/kernel/ftrace.c 2008-10-24 16:35:48.000000000 +0600
+++ linux-2.6/arch/x86/kernel/ftrace.c 2008-10-24 16:40:09.000000000 +0600
@@ -129,7 +129,7 @@ int __init ftrace_dyn_arch_init(void *da
asm volatile (
"jmp ftrace_test_jmp\n"
/* This code needs to stay around */
- ".section .text, \"ax\"\n"
+ ".section .text.init, \"ax\"\n"
"ftrace_test_jmp:"
"jmp ftrace_test_p6nop\n"
"nop\n"
>
> Ingo
>
* Rakib Mullick <[email protected]> wrote:
> Does the following solves the problem?
> Thanks.
>
> --- linux-2.6-orig/arch/x86/kernel/ftrace.c 2008-10-24 16:35:48.000000000 +0600
> +++ linux-2.6/arch/x86/kernel/ftrace.c 2008-10-24 16:40:09.000000000 +0600
> @@ -129,7 +129,7 @@ int __init ftrace_dyn_arch_init(void *da
> asm volatile (
> "jmp ftrace_test_jmp\n"
> /* This code needs to stay around */
> - ".section .text, \"ax\"\n"
> + ".section .text.init, \"ax\"\n"
how about the "This code needs to stay around" comment?
Ingo
On Fri, 24 Oct 2008, Ingo Molnar wrote:
>
> * Rakib Mullick <[email protected]> wrote:
>
> > Does the following solves the problem?
> > Thanks.
> >
> > --- linux-2.6-orig/arch/x86/kernel/ftrace.c 2008-10-24 16:35:48.000000000 +0600
> > +++ linux-2.6/arch/x86/kernel/ftrace.c 2008-10-24 16:40:09.000000000 +0600
> > @@ -129,7 +129,7 @@ int __init ftrace_dyn_arch_init(void *da
> > asm volatile (
> > "jmp ftrace_test_jmp\n"
> > /* This code needs to stay around */
> > - ".section .text, \"ax\"\n"
> > + ".section .text.init, \"ax\"\n"
>
> how about the "This code needs to stay around" comment?
Yes that is correct. That part can not be converted into .init.
The code is used later at run time when the tracer is enabled and we
patch the code back to a call to mcount. We use this code as to know what
we should expect should be at the nop locations. But that code is used
later as data and not exectude, which means that we do not need to worry
about it calling back into the .init section.
If you only want to get rid of the section mismatch warning. Just remove
the __init from the "ftrace_dyn_arch_init" function. But then we are just
wasting those bytes that will never be used again.
The real solution should probably be this:
(Compiled tested only)
Signed-off-by: Steven Rostedt <[email protected]>
---
arch/x86/kernel/ftrace.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
Index: linux-tip.git/arch/x86/kernel/ftrace.c
===================================================================
--- linux-tip.git.orig/arch/x86/kernel/ftrace.c 2008-10-23 19:23:28.000000000 -0400
+++ linux-tip.git/arch/x86/kernel/ftrace.c 2008-10-24 08:11:57.000000000 -0400
@@ -22,7 +22,7 @@
/* Long is fine, even if it is only 4 bytes ;-) */
-static unsigned long *ftrace_nop;
+static unsigned long ftrace_nop[MCOUNT_INSN_SIZE];
union ftrace_code_union {
char code[MCOUNT_INSN_SIZE];
@@ -126,8 +126,7 @@ int __init ftrace_dyn_arch_init(void *da
*/
asm volatile (
"jmp ftrace_test_jmp\n"
- /* This code needs to stay around */
- ".section .text, \"ax\"\n"
+ ".section .text.init, \"ax\"\n"
"ftrace_test_jmp:"
"jmp ftrace_test_p6nop\n"
"nop\n"
@@ -154,15 +153,15 @@ int __init ftrace_dyn_arch_init(void *da
switch (faulted) {
case 0:
pr_info("ftrace: converting mcount calls to 0f 1f 44 00 00\n");
- ftrace_nop = (unsigned long *)ftrace_test_p6nop;
+ memcpy(ftrace_nop, ftrace_test_p6nop, MCOUNT_INSN_SIZE);
break;
case 1:
pr_info("ftrace: converting mcount calls to 66 66 66 66 90\n");
- ftrace_nop = (unsigned long *)ftrace_test_nop5;
+ memcpy(ftrace_nop, ftrace_test_nop5, MCOUNT_INSN_SIZE);
break;
case 2:
pr_info("ftrace: converting mcount calls to jmp . + 5\n");
- ftrace_nop = (unsigned long *)ftrace_test_jmp;
+ memcpy(ftrace_nop, ftrace_test_jmp, MCOUNT_INSN_SIZE);
break;
}
On Fri, 24 Oct 2008, Steven Rostedt wrote:
>
> The real solution should probably be this:
>
> (Compiled tested only)
>
> Signed-off-by: Steven Rostedt <[email protected]>
> ---
> arch/x86/kernel/ftrace.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> Index: linux-tip.git/arch/x86/kernel/ftrace.c
> ===================================================================
> --- linux-tip.git.orig/arch/x86/kernel/ftrace.c 2008-10-23 19:23:28.000000000 -0400
> +++ linux-tip.git/arch/x86/kernel/ftrace.c 2008-10-24 08:11:57.000000000 -0400
> @@ -22,7 +22,7 @@
>
>
> /* Long is fine, even if it is only 4 bytes ;-) */
> -static unsigned long *ftrace_nop;
> +static unsigned long ftrace_nop[MCOUNT_INSN_SIZE];
I need to convert that to unsigned char ftrace_nop[]. I'll run some more
tests, and produce a real patch later.
-- Steve
>
> union ftrace_code_union {
> char code[MCOUNT_INSN_SIZE];
> @@ -126,8 +126,7 @@ int __init ftrace_dyn_arch_init(void *da
> */
> asm volatile (
> "jmp ftrace_test_jmp\n"
> - /* This code needs to stay around */
> - ".section .text, \"ax\"\n"
> + ".section .text.init, \"ax\"\n"
> "ftrace_test_jmp:"
> "jmp ftrace_test_p6nop\n"
> "nop\n"
> @@ -154,15 +153,15 @@ int __init ftrace_dyn_arch_init(void *da
> switch (faulted) {
> case 0:
> pr_info("ftrace: converting mcount calls to 0f 1f 44 00 00\n");
> - ftrace_nop = (unsigned long *)ftrace_test_p6nop;
> + memcpy(ftrace_nop, ftrace_test_p6nop, MCOUNT_INSN_SIZE);
> break;
> case 1:
> pr_info("ftrace: converting mcount calls to 66 66 66 66 90\n");
> - ftrace_nop = (unsigned long *)ftrace_test_nop5;
> + memcpy(ftrace_nop, ftrace_test_nop5, MCOUNT_INSN_SIZE);
> break;
> case 2:
> pr_info("ftrace: converting mcount calls to jmp . + 5\n");
> - ftrace_nop = (unsigned long *)ftrace_test_jmp;
> + memcpy(ftrace_nop, ftrace_test_jmp, MCOUNT_INSN_SIZE);
> break;
> }
>
>
The dynamic ftrace determines which nop is safe to use at start up.
When it finds a safe nop for patching, it sets a pointer called ftrace_nop
to point to the code. All call sites are then patched to this nop.
Later, when tracing is turned on, this ftrace_nop variable is again used
to compare the location to make sure it is a nop before we update it to
a mcount call. If this fails just once, a warning is outputed and ftrace
is disabled.
Rakib Mullick noted that the code that sets up the nop is a .init section
where as the nop itself is in the .text section. This is needed because
the nop is used later on after boot up. The problem is that the test of the
nop jumps back to the setup code and causes a "section mismatch" warning.
Rabik first recommended to convert the nop to .init.text, but as stated
above, this would fail since that text is used later.
The real solution is to extend Rabik's patch, and to make the ftrace_nop
into an array, and just save the code from the assembly to this array.
Now the section can stay as an init section, and we have a nop to use
later on.
Signed-off-by: Steven Rostedt <[email protected]>
---
arch/x86/kernel/ftrace.c | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
Index: linux-tip.git/arch/x86/kernel/ftrace.c
===================================================================
--- linux-tip.git.orig/arch/x86/kernel/ftrace.c 2008-10-23 19:23:28.000000000 -0400
+++ linux-tip.git/arch/x86/kernel/ftrace.c 2008-10-24 08:51:59.000000000 -0400
@@ -21,8 +21,7 @@
#include <asm/nops.h>
-/* Long is fine, even if it is only 4 bytes ;-) */
-static unsigned long *ftrace_nop;
+static unsigned char ftrace_nop[MCOUNT_INSN_SIZE];
union ftrace_code_union {
char code[MCOUNT_INSN_SIZE];
@@ -40,7 +39,7 @@ static int ftrace_calc_offset(long ip, l
unsigned char *ftrace_nop_replace(void)
{
- return (char *)ftrace_nop;
+ return ftrace_nop;
}
unsigned char *ftrace_call_replace(unsigned long ip, unsigned long addr)
@@ -125,9 +124,6 @@ int __init ftrace_dyn_arch_init(void *da
* TODO: check the cpuid to determine the best nop.
*/
asm volatile (
- "jmp ftrace_test_jmp\n"
- /* This code needs to stay around */
- ".section .text, \"ax\"\n"
"ftrace_test_jmp:"
"jmp ftrace_test_p6nop\n"
"nop\n"
@@ -138,8 +134,6 @@ int __init ftrace_dyn_arch_init(void *da
"jmp 1f\n"
"ftrace_test_nop5:"
".byte 0x66,0x66,0x66,0x66,0x90\n"
- "jmp 1f\n"
- ".previous\n"
"1:"
".section .fixup, \"ax\"\n"
"2: movl $1, %0\n"
@@ -154,15 +148,15 @@ int __init ftrace_dyn_arch_init(void *da
switch (faulted) {
case 0:
pr_info("ftrace: converting mcount calls to 0f 1f 44 00 00\n");
- ftrace_nop = (unsigned long *)ftrace_test_p6nop;
+ memcpy(ftrace_nop, ftrace_test_p6nop, MCOUNT_INSN_SIZE);
break;
case 1:
pr_info("ftrace: converting mcount calls to 66 66 66 66 90\n");
- ftrace_nop = (unsigned long *)ftrace_test_nop5;
+ memcpy(ftrace_nop, ftrace_test_nop5, MCOUNT_INSN_SIZE);
break;
case 2:
pr_info("ftrace: converting mcount calls to jmp . + 5\n");
- ftrace_nop = (unsigned long *)ftrace_test_jmp;
+ memcpy(ftrace_nop, ftrace_test_jmp, MCOUNT_INSN_SIZE);
break;
}
On Fri, 24 Oct 2008, Steven Rostedt wrote:
>
> The dynamic ftrace determines which nop is safe to use at start up.
> When it finds a safe nop for patching, it sets a pointer called ftrace_nop
> to point to the code. All call sites are then patched to this nop.
>
> Later, when tracing is turned on, this ftrace_nop variable is again used
> to compare the location to make sure it is a nop before we update it to
> a mcount call. If this fails just once, a warning is outputed and ftrace
> is disabled.
>
> Rakib Mullick noted that the code that sets up the nop is a .init section
> where as the nop itself is in the .text section. This is needed because
> the nop is used later on after boot up. The problem is that the test of the
> nop jumps back to the setup code and causes a "section mismatch" warning.
>
> Rabik first recommended to convert the nop to .init.text, but as stated
> above, this would fail since that text is used later.
>
> The real solution is to extend Rabik's patch, and to make the ftrace_nop
> into an array, and just save the code from the assembly to this array.
Rereading what I sent, I see I misspelled Rakib's name twice.
Ingo, could you fix the changelog here before commiting it.
Thanks,
-- Steve
* Steven Rostedt <[email protected]> wrote:
>
> On Fri, 24 Oct 2008, Steven Rostedt wrote:
>
> >
> > The dynamic ftrace determines which nop is safe to use at start up.
> > When it finds a safe nop for patching, it sets a pointer called ftrace_nop
> > to point to the code. All call sites are then patched to this nop.
> >
> > Later, when tracing is turned on, this ftrace_nop variable is again used
> > to compare the location to make sure it is a nop before we update it to
> > a mcount call. If this fails just once, a warning is outputed and ftrace
> > is disabled.
> >
> > Rakib Mullick noted that the code that sets up the nop is a .init section
> > where as the nop itself is in the .text section. This is needed because
> > the nop is used later on after boot up. The problem is that the test of the
> > nop jumps back to the setup code and causes a "section mismatch" warning.
> >
> > Rabik first recommended to convert the nop to .init.text, but as stated
> > above, this would fail since that text is used later.
> >
> > The real solution is to extend Rabik's patch, and to make the ftrace_nop
> > into an array, and just save the code from the assembly to this array.
>
> Rereading what I sent, I see I misspelled Rakib's name twice.
>
> Ingo, could you fix the changelog here before commiting it.
done - find the tip/tracing/urgent commit below. I also added an
Impact: line.
Ingo
---------------->
>From 8115f3f0c939c5db0fe3c6c6c58911fd3a205b1e Mon Sep 17 00:00:00 2001
From: Steven Rostedt <[email protected]>
Date: Fri, 24 Oct 2008 09:12:17 -0400
Subject: [PATCH] ftrace: use a real variable for ftrace_nop in x86
Impact: avoid section mismatch warning, clean up
The dynamic ftrace determines which nop is safe to use at start up.
When it finds a safe nop for patching, it sets a pointer called ftrace_nop
to point to the code. All call sites are then patched to this nop.
Later, when tracing is turned on, this ftrace_nop variable is again used
to compare the location to make sure it is a nop before we update it to
an mcount call. If this fails just once, a warning is printed and ftrace
is disabled.
Rakib Mullick noted that the code that sets up the nop is a .init section
where as the nop itself is in the .text section. This is needed because
the nop is used later on after boot up. The problem is that the test of the
nop jumps back to the setup code and causes a "section mismatch" warning.
Rakib first recommended to convert the nop to .init.text, but as stated
above, this would fail since that text is used later.
The real solution is to extend Rabik's patch, and to make the ftrace_nop
into an array, and just save the code from the assembly to this array.
Now the section can stay as an init section, and we have a nop to use
later on.
Reported-by: Rakib Mullick <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
---
arch/x86/kernel/ftrace.c | 16 +++++-----------
1 files changed, 5 insertions(+), 11 deletions(-)
diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
index b1e5e22..50ea0ac 100644
--- a/arch/x86/kernel/ftrace.c
+++ b/arch/x86/kernel/ftrace.c
@@ -21,8 +21,7 @@
#include <asm/nops.h>
-/* Long is fine, even if it is only 4 bytes ;-) */
-static unsigned long *ftrace_nop;
+static unsigned char ftrace_nop[MCOUNT_INSN_SIZE];
union ftrace_code_union {
char code[MCOUNT_INSN_SIZE];
@@ -40,7 +39,7 @@ static int ftrace_calc_offset(long ip, long addr)
unsigned char *ftrace_nop_replace(void)
{
- return (char *)ftrace_nop;
+ return ftrace_nop;
}
unsigned char *ftrace_call_replace(unsigned long ip, unsigned long addr)
@@ -125,9 +124,6 @@ int __init ftrace_dyn_arch_init(void *data)
* TODO: check the cpuid to determine the best nop.
*/
asm volatile (
- "jmp ftrace_test_jmp\n"
- /* This code needs to stay around */
- ".section .text, \"ax\"\n"
"ftrace_test_jmp:"
"jmp ftrace_test_p6nop\n"
"nop\n"
@@ -138,8 +134,6 @@ int __init ftrace_dyn_arch_init(void *data)
"jmp 1f\n"
"ftrace_test_nop5:"
".byte 0x66,0x66,0x66,0x66,0x90\n"
- "jmp 1f\n"
- ".previous\n"
"1:"
".section .fixup, \"ax\"\n"
"2: movl $1, %0\n"
@@ -154,15 +148,15 @@ int __init ftrace_dyn_arch_init(void *data)
switch (faulted) {
case 0:
pr_info("ftrace: converting mcount calls to 0f 1f 44 00 00\n");
- ftrace_nop = (unsigned long *)ftrace_test_p6nop;
+ memcpy(ftrace_nop, ftrace_test_p6nop, MCOUNT_INSN_SIZE);
break;
case 1:
pr_info("ftrace: converting mcount calls to 66 66 66 66 90\n");
- ftrace_nop = (unsigned long *)ftrace_test_nop5;
+ memcpy(ftrace_nop, ftrace_test_nop5, MCOUNT_INSN_SIZE);
break;
case 2:
pr_info("ftrace: converting mcount calls to jmp . + 5\n");
- ftrace_nop = (unsigned long *)ftrace_test_jmp;
+ memcpy(ftrace_nop, ftrace_test_jmp, MCOUNT_INSN_SIZE);
break;
}