From: ilya@theIlya.com
To: linux-mips@linux-mips.org
Subject: Re: Yet another fix
Date: Sun, 1 Jun 2003 21:57:00 -0700 [thread overview]
Message-ID: <20030602045700.GI3035@gateway.total-knowledge.com> (raw)
In-Reply-To: <13249.1054529364@kao2.melbourne.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
module_map is referenced in register_ioctl32_conversion in arch/mips64/ioctl32.c
As far as I can see, it should simply be possible to replace module_map
with vmalloc in there, but I am not sure, as I don't know how exactly
ioctl translations work...
On Mon, Jun 02, 2003 at 02:49:24PM +1000, Keith Owens wrote:
> On Sun, 1 Jun 2003 21:14:24 -0700,
> ilya@theIlya.com wrote:
> >I am not sure this is correct solution to a problem. Or rather, I'm pretty
> >sure it is incorrect one.. There is a reference to module_map somewhere, however
> >it is not inculded if modules are disabled. Here is sorta fix
> >
> >Index: include/asm-mips64/module.h
> >===================================================================
> >RCS file: /home/cvs/linux/include/asm-mips64/module.h,v
> >retrieving revision 1.5
> >diff -u -r1.5 module.h
> >--- include/asm-mips64/module.h 1 Jun 2003 00:39:15 -0000 1.5
> >+++ include/asm-mips64/module.h 2 Jun 2003 03:59:23 -0000
> >@@ -11,4 +11,8 @@
> > #define Elf_Sym Elf32_Sym
> > #define Elf_Ehdr Elf32_Ehdr
> >
> >+#ifndef CONFIG_MODULES
> >+#define module_map(x) vmalloc(x)
> >+#endif
> >+
> > #endif /* _ASM_MODULE_H */
>
> That fix is incorrect. There should be no references to module_map
> when CONFIG_MODULES=n. Please find out where module_map is being
> incorrectly used and fix that code.
>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-02 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 4:14 Yet another fix ilya
2003-06-02 4:49 ` Keith Owens
2003-06-02 4:57 ` ilya [this message]
2003-06-02 13:27 ` Keith Owens
2003-06-02 14:12 ` Ralf Baechle
2003-06-02 14:30 ` ilya
2003-06-02 23:50 ` Keith Owens
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=20030602045700.GI3035@gateway.total-knowledge.com \
--to=ilya@theilya.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.