From: Andrew Morton <akpm@digeo.com>
To: Pawel Kot <pkot@bezsensu.pl>, Rusty Russell <rusty@rustcorp.com.au>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Anton Altaparmakov" <aia21@cantab.net>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.45: NTFS unresolved symbol
Date: Fri, 01 Nov 2002 11:48:48 -0800 [thread overview]
Message-ID: <3DC2DAA0.A46C5085@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.33.0211011318270.5622-100000@urtica.linuxnews.pl
Pawel Kot wrote:
>
> On Fri, 1 Nov 2002, Dieter [iso-8859-15] Nützel wrote:
>
> > depmod: *** Unresolved symbols in /lib/modules/2.5.45/kernel/fs/ntfs/ntfs.o
> > depmod: page_states__per_cpu
> > /lib/modules/2.5.45/kernel/fs/ntfs/ntfs.o
>
> Hi, The following patch should fix it:
> --- kernel/ksyms.c~ Fri Nov 1 13:16:51 2002
> +++ kernel/ksyms.c Fri Nov 1 13:16:51 2002
> @@ -112,6 +112,7 @@
> EXPORT_SYMBOL(vunmap);
> EXPORT_SYMBOL(vmalloc_to_page);
> EXPORT_SYMBOL(remap_page_range);
> +EXPORT_SYMBOL(page_states__per_cpu);
> #ifndef CONFIG_DISCONTIGMEM
> EXPORT_SYMBOL(contig_page_data);
> EXPORT_SYMBOL(mem_map);
Oh gawd. Here's what happened..
We have these magical symbols which describe the offset of
a member of the per-cpu storage, which need to be exposed
to modules. So I added an EXPORT_PER_CPU_SYMBOL() helper:
#define EXPORT_PER_CPU_SYMBOL(var) EXPORT_SYMBOL(var##__per_cpu)
#define EXPORT_PER_CPU_SYMBOL_GPL(var) EXPORT_SYMBOL_GPL(var##__per_cpu)
Which works OK without module versioning. But with module versioning,
genksyms goes looking through source files for "EXPORT_SYMBOL". Which
isn't there.
So sigh. Need to go back to the drawing board on that one. In
the meantime, this should work?
--- 25/mm/page_alloc.c~genksyms-hurts Fri Nov 1 11:47:42 2002
+++ 25-akpm/mm/page_alloc.c Fri Nov 1 11:47:53 2002
@@ -650,7 +650,7 @@ unsigned int nr_free_highpages (void)
* during and after execution of this function.
*/
DEFINE_PER_CPU(struct page_state, page_states) = {0};
-EXPORT_PER_CPU_SYMBOL(page_states);
+EXPORT_SYMBOL(page_states__per_cpu);
void __get_page_state(struct page_state *ret, int nr)
{
.
next prev parent reply other threads:[~2002-11-01 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 3:31 2.5.45: NTFS unresolved symbol Dieter Nützel
2002-11-01 12:20 ` Pawel Kot
2002-11-01 19:48 ` Andrew Morton [this message]
2002-11-01 20:00 ` Sam Ravnborg
2002-11-01 22:24 ` Rusty Russell
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=3DC2DAA0.A46C5085@digeo.com \
--to=akpm@digeo.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pkot@bezsensu.pl \
--cc=rusty@rustcorp.com.au \
/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