Re: Detecting section mismatches in vmlinux

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Atsushi Nemoto
Date: Sunday, February 25, 2007 - 8:48 am

On Sun, 25 Feb 2007 00:25:27 +0100, Sam Ravnborg <sam@ravnborg.org> wrote:

Thanks!  It works fine for me too.


This is because rest_init() (non __init) references 'init' (__init) as
an argument of kernel_thread().  No idea how to avoid this warning...


This is because set_up_list3s() (non __init) references
initkmem_list3[] (__initdata).  The set_up_list3s() is only used on
early stage so can be __init, but it cause an another mismatch ---
setup_cpu_cache() (non __init) calls __init function.  Some trick
using a function pointer might solve this issue, but I wonder it is a
right thing to do...

Or we need another whitelist for vmlinux?

---
Atsushi Nemoto
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Detecting section mismatches in vmlinux, Atsushi Nemoto, (Wed Feb 21, 8:57 am)
Re: Detecting section mismatches in vmlinux, Atsushi Nemoto, (Sat Feb 24, 11:53 am)
Re: Detecting section mismatches in vmlinux, Sam Ravnborg, (Sat Feb 24, 1:07 pm)
Re: Detecting section mismatches in vmlinux, Sam Ravnborg, (Sat Feb 24, 4:25 pm)
Re: Detecting section mismatches in vmlinux, Atsushi Nemoto, (Sun Feb 25, 8:48 am)
[PATCH] x86_64: fix section mismatch warnings, Sam Ravnborg, (Sun Feb 25, 1:53 pm)
Re: [PATCH] x86_64: fix section mismatch warnings, Andrew Morton, (Tue Feb 27, 1:25 pm)