[PATCH 0/4] elf core: Write section header table first

From: HATAYAMA Daisuke
Date: Wed Dec 29 2010 - 16:16:26 EST


This patchset changes a position of section header table, if exists,
from the last to the next to ELF header. According to ELF
specification, the order of ELF component layout is not specified
except for ELF header. See:

http://www.sco.com/developers/gabi/latest/ch4.intro.html#file_format

The merits are:
- reducing tracing memory maps from 3 times to 2 times.
- simple offset handling that makes the code easier to read.

arch/ia64/kernel/elfcore.c | 16 -----
arch/um/sys-i386/elfcore.c | 16 -----
fs/binfmt_elf.c | 136 +++++++++++++++++-------------------------
fs/binfmt_elf_fdpic.c | 141 ++++++++++++++++++--------------------------
include/linux/elfcore.h | 1 -
kernel/elfcore.c | 5 --
6 files changed, 111 insertions(+), 204 deletions(-)

I built and tested this patchset on x86_64. I also built it on ia64,
um-i386 and frv using cross compilers to cover the range.

Here's a program useful to generate ELF core with many program header
entries, and three steps to produce such ELF core:

$ sysctl vm.max_map_count=70000
$ ulimit -c unlimted
$ mkmmap 65535

== mkmmap.c
#include <stdio.h>
#include <stdlib.h>
#include <sys/mman.h>
#include <fcntl.h>
#include <unistd.h>
int main(int argc, char **argv)
{
int maps_num;
if (argc < 2) {
fprintf(stderr, "mkmmaps [number of maps to be created]\n");
exit(1);
}
if (sscanf(argv[1], "%d", &maps_num) == EOF) {
perror("sscanf");
exit(2);
}
if (maps_num < 0) {
fprintf(stderr, "%d is invalid\n", maps_num);
exit(3);
}
for (; maps_num > 0; --maps_num) {
if (MAP_FAILED == mmap((void *)NULL, (size_t) 1, PROT_READ,
MAP_SHARED | MAP_ANONYMOUS, (int) -1,
(off_t) NULL)) {
perror("mmap");
exit(4);
}
}
abort();
{
char buffer[128];
sprintf(buffer, "wc -l /proc/%u/maps", getpid());
system(buffer);
}
return 0;
}
==

Signed-off-by: HATAYAMA Daisuke <d.hatayama@xxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/