All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: alan@lxorguk.ukuu.org.uk, marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] binfmt_elf as module
Date: Sat, 23 Feb 2002 07:11:42 -0500	[thread overview]
Message-ID: <3C7786FE.6828F4BF@yahoo.com> (raw)

[-- Attachment #1: ksyms --]
[-- Type: text/plain, Size: 1575 bytes --]


Someone reported binfmt_elf.o wouldn't load because of unresolved symbols,
but didn't report the symbols that were missing (I seem to have deleted 
the original mail.)

Turns out it is empty_zero_page and get_user_pages that are missing.
Probably been broken for ages, as binfmt_elf is compiled in for 99.9% 
of folks of course.

Patch for i386 against 2.4.17 follows.  Other arch may also still be broken,
depending on their definition of ZERO_PAGE and whether or not it uses 
empty_zero_page.

Paul.

--- mm/Makefile~	Tue Nov  6 19:14:49 2001
+++ mm/Makefile	Sat Feb 23 06:30:04 2002
@@ -9,7 +9,7 @@
 
 O_TARGET := mm.o
 
-export-objs := shmem.o filemap.o
+export-objs := shmem.o filemap.o memory.o
 
 obj-y	 := memory.o mmap.o filemap.o mprotect.o mlock.o mremap.o \
 	    vmalloc.o slab.o bootmem.o swap.o vmscan.o page_io.o \
--- arch/i386/kernel/i386_ksyms.c~	Sat Feb  2 06:43:30 2002
+++ arch/i386/kernel/i386_ksyms.c	Sat Feb 23 06:23:33 2002
@@ -71,6 +71,7 @@
 EXPORT_SYMBOL(get_cmos_time);
 EXPORT_SYMBOL(apm_info);
 EXPORT_SYMBOL(gdt);
+EXPORT_SYMBOL(empty_zero_page);
 
 #ifdef CONFIG_DEBUG_IOVIRT
 EXPORT_SYMBOL(__io_virt_debug);
--- mm/memory.c~	Sat Feb  2 06:51:18 2002
+++ mm/memory.c	Sat Feb 23 06:28:36 2002
@@ -44,6 +44,7 @@
 #include <linux/iobuf.h>
 #include <linux/highmem.h>
 #include <linux/pagemap.h>
+#include <linux/module.h>
 
 #include <asm/pgalloc.h>
 #include <asm/uaccess.h>
@@ -499,6 +500,8 @@
 	} while(len);
 	return i;
 }
+
+EXPORT_SYMBOL(get_user_pages);
 
 /*
  * Force in an entire range of pages from the current process's user VA,




                 reply	other threads:[~2002-02-23 12:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C7786FE.6828F4BF@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.