From: Andrew Morton <akpm@digeo.com>
To: kronos@kronoz.cjb.net
Cc: lord@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5.47] Unable to load XFS module
Date: Wed, 13 Nov 2002 11:21:02 -0800 [thread overview]
Message-ID: <3DD2A61E.F0647BD4@digeo.com> (raw)
In-Reply-To: 20021113184805.GA777@dreamland.darkstar.net
Kronos wrote:
>
> Hi,
> I'm playing with kernel 2.5.47. XFS support is compiled as module and at
> boot time, while mounting /home, I get this:
>
> insmod /lib/modules/2.5.47/kernel/fs/xfs/xfs.o failed
>
> Then, trying to modprobe xfs by hand:
>
> /lib/modules/2.5.47/kernel/fs/xfs/xfs.o: unresolved symbol page_states__per_cpu
> /lib/modules/2.5.47/kernel/fs/xfs/xfs.o: insmod /lib/modules/2.5.47/kernel/fs/xfs/xfs.o failed
> /lib/modules/2.5.47/kernel/fs/xfs/xfs.o: insmod xfs failed
>
You'll need to disable module symbol versioning, or apply this
patch from Rusty:
include/asm-generic/percpu.h | 6 ++++++
1 files changed, 6 insertions(+)
--- 25/include/asm-generic/percpu.h~genksyms-fix Wed Nov 13 00:57:06 2002
+++ 25-akpm/include/asm-generic/percpu.h Wed Nov 13 00:57:06 2002
@@ -35,4 +35,10 @@ extern unsigned long __per_cpu_offset[NR
#define EXPORT_PER_CPU_SYMBOL(var) EXPORT_SYMBOL(var##__per_cpu)
#define EXPORT_PER_CPU_SYMBOL_GPL(var) EXPORT_SYMBOL_GPL(var##__per_cpu)
+/* Genksyms can't follow the percpu declaration. Give it a fake one. */
+#ifdef __GENKSYMS__
+#undef DEFINE_PER_CPU
+#define DEFINE_PER_CPU(type, name) type name##__per_cpu
+#endif /*__GENKSYMS__*/
+
#endif /* _ASM_GENERIC_PERCPU_H_ */
_
prev parent reply other threads:[~2002-11-13 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 18:48 [2.5.47] Unable to load XFS module Kronos
2002-11-13 19:19 ` Stephen Lord
2002-11-13 19:21 ` Andrew Morton [this message]
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=3DD2A61E.F0647BD4@digeo.com \
--to=akpm@digeo.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
/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).