From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] disallow modular BINFMT_ELF
Date: Sun, 16 Nov 2003 00:26:04 +0100 [thread overview]
Message-ID: <20031115232600.GF7919@fs.tum.de> (raw)
modular BINFMT_ELF gives unresolved symbols in 2.4 .
modular BINFMT_ELF gives the following unresolved symbols in 2.6:
<-- snip -->
WARNING: /lib/modules/2.6.0-test9-mm3/kernel/fs/binfmt_elf.ko needs
unknown symbol __kernel_vsyscall
WARNING: /lib/modules/2.6.0-test9-mm3/kernel/fs/binfmt_elf.ko needs
unknown symbol empty_zero_page
WARNING: /lib/modules/2.6.0-test9-mm3/kernel/fs/binfmt_elf.ko needs
unknown symbol dump_task_fpu
WARNING: /lib/modules/2.6.0-test9-mm3/kernel/fs/binfmt_elf.ko needs
unknown symbol dump_task_extended_fpu
WARNING: /lib/modules/2.6.0-test9-mm3/kernel/fs/binfmt_elf.ko needs
unknown symbol dump_task_regs
<-- snip -->
Since modular BINFMT_ELF is pretty pathological I'd suggest the
following patch:
--- linux-2.6.0-test9-mm3/fs/Kconfig.binfmt.old 2003-11-15 23:43:24.000000000 +0100
+++ linux-2.6.0-test9-mm3/fs/Kconfig.binfmt 2003-11-15 23:43:49.000000000 +0100
@@ -1,5 +1,5 @@
config BINFMT_ELF
- tristate "Kernel support for ELF binaries"
+ bool "Kernel support for ELF binaries"
depends on MMU
default y
---help---
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2003-11-15 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 23:26 Adrian Bunk [this message]
2003-11-15 23:48 ` [2.6 patch] disallow modular BINFMT_ELF Jeff Garzik
2003-11-15 23:53 ` Martin Hicks
2003-11-17 1:09 ` Eric W. Biederman
2003-11-17 13:08 ` Jakub Jelinek
2003-11-17 9:25 ` Christoph Hellwig
2003-11-17 9:26 ` Christoph Hellwig
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=20031115232600.GF7919@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--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