Messages in this thread Patch in this message | | | Date | Sat, 8 Jul 2006 20:05:54 +0200 | From | Christoph Hellwig <> | Subject | [PATCH 2/3] disallow modular binfmt_elf32 |
| |
Currently most architectures either always build binfmt_elf32 in the kernel image or make it a boolean option. Only sparc64 and s390 allow to build it modularly. This patch turns the option into a boolean aswell because elf requires various symbols that shouldn't be available to modules. The most urgent one is tasklist_lock whos export this patch series kills, but there are others like force_sgi aswell.
Note that sparc doesn't allow a modular 32bit a.out handler either, and that would be the more useful case as only few people want 32bit sunos compatibility and 99.9% of all sparc64 users need 32bit linux native elf support.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/arch/s390/Kconfig =================================================================== --- linux-2.6.orig/arch/s390/Kconfig 2006-07-06 14:21:17.000000000 +0200 +++ linux-2.6/arch/s390/Kconfig 2006-07-08 19:08:46.000000000 +0200 @@ -119,7 +119,7 @@ default y config BINFMT_ELF32 - tristate "Kernel support for 31 bit ELF binaries" + bool "Kernel support for 31 bit ELF binaries" depends on COMPAT help This allows you to run 32-bit Linux/ELF binaries on your zSeries Index: linux-2.6/arch/sparc64/Kconfig =================================================================== --- linux-2.6.orig/arch/sparc64/Kconfig 2006-07-01 12:49:02.000000000 +0200 +++ linux-2.6/arch/sparc64/Kconfig 2006-07-08 19:08:32.000000000 +0200 @@ -334,7 +334,7 @@ default y config BINFMT_ELF32 - tristate "Kernel support for 32-bit ELF binaries" + bool "Kernel support for 32-bit ELF binaries" depends on SPARC32_COMPAT help This allows you to run 32-bit Linux/ELF binaries on your Ultra. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |