From: Yura Pakhuchiy <Cha0sMaster@tut.by>
To: linux-kernel@vger.kernel.org
Cc: Anton Altaparmakov <aia21@cam.ac.uk>
Subject: Re: ntfs.ko needs unknown symbol end_iomem (under uml)
Date: Thu, 21 Oct 2004 17:44:46 +0300 [thread overview]
Message-ID: <4177CB5E.7000503@tut.by> (raw)
In-Reply-To: <1098367622.10371.13.camel@imp.csi.cam.ac.uk>
Hi,
Anton Altaparmakov wrote:
> On Thu, 2004-10-21 at 14:53, Yura Pakhuchiy wrote:
>
>>Hi Anton,
>>
>>When I compile ntfs as module for UML I receive during build:
>>*** Warning: "end_iomem" [fs/ntfs/ntfs.ko] undefined!
>>
>>It's ntfs bug or uml bug? Or am I doing something wrong?
>
>
> UML is broken. It defines VMALLOC_START to ((end_iomem +
> VMALLOC_OFFSET) & ~(VMALLOC_OFFSET-1)) but it clearly does not export
> end_iomem to modules which means modules cannot use VMALLOC_START.
>
> But ntfs uses VMALLOC_START to determine if a pointer is in kmalloc()-ed
> memory or vmalloc()-ed memory so if you want to build it as a module you
> need to fix uml to export end_iomem, i.e. by for example adding:
>
> EXPORT_SYMBOL(end_iomem);
>
> after the end_iomem definition in arch/um/kernel/um_arch.c and the
> reconfiguring, recbuilding the kernel.
>
> You may wish to report this to LKML / the UML maintainer (after you have
> made sure that this does actually fix it).
>
> Best regards,
>
> Anton
I didn't find UML maintainer in MAINTAINERS, so I send this to
linux-kernel@vger.kernel.org.
I added line that Anton suggested and it's fixed above bug. Patch below.
Best regards,
Yura
--- ntfs-2.6-devel/arch/um/kernel/um_arch.c 2004-10-19 20:50:05.000000000 +0300
+++ ntfs-2.6-yura/arch/um/kernel/um_arch.c 2004-10-21 17:14:18.000000000 +0300
@@ -300,6 +300,7 @@ static void __init uml_postsetup(void)
/* Set during early boot */
unsigned long brk_start;
unsigned long end_iomem;
+EXPORT_SYMBOL(end_iomem);
#define MIN_VMALLOC (32 * 1024 * 1024)
parent reply other threads:[~2004-10-21 14:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1098367622.10371.13.camel@imp.csi.cam.ac.uk>]
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=4177CB5E.7000503@tut.by \
--to=cha0smaster@tut.by \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome