The patch titled
Elf loader crash while zero-filling .bss
has been removed from the -mm tree. Its filename was
elf-loader-crash-while-zero-filling-bss.patch
This patch was dropped because it was nacked
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: Elf loader crash while zero-filling .bss
From: "Abel Bernabeu" <abelbg@xxxxxxxxx>
I've finally found a solution for the crash in load_binary_elf I
reported last week:
http://lkml.org/lkml/2008/1/30/171
The attached patch solves my problem.
set_brk(start, end) allocs just page aligned regions (by "collapsing" both
extremes to the start of the page in which they lay)... That means than
even if both pointers are not equal there are still some chances that
set_brk has allocated no space at all because ELF_PAGEALIGN(elf_bss) ==
ELF_PAGEALIGN(elf_brk).
So the condition was not correct.
Cc: Roland McGrath <roland@xxxxxxxxxx>
Cc: Daniel Jacobowitz <dan@xxxxxxxxxx>
Cc: Jiri Kosina <jkosina@xxxxxxx>
Cc: "H. Peter Anvin" <hpa@xxxxxxxxx>
Cc: Andreas Schwab <schwab@xxxxxxx>
Cc: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/binfmt_elf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN fs/binfmt_elf.c~elf-loader-crash-while-zero-filling-bss fs/binfmt_elf.c
--- a/fs/binfmt_elf.c~elf-loader-crash-while-zero-filling-bss
+++ a/fs/binfmt_elf.c
@@ -893,7 +893,8 @@ static int load_elf_binary(struct linux_
send_sig(SIGKILL, current, 0);
goto out_free_dentry;
}
- if (likely(elf_bss != elf_brk) && unlikely(padzero(elf_bss))) {
+ if (likely(ELF_PAGEALIGN(elf_bss) != ELF_PAGEALIGN(elf_brk)) &&
+ unlikely(padzero(elf_bss))) {
send_sig(SIGSEGV, current, 0);
retval = -EFAULT; /* Nobody gets to see this, but.. */
goto out_free_dentry;
_
Patches currently in -mm which might be from abelbg@xxxxxxxxx are
elf-loader-crash-while-zero-filling-bss.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
