summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorHaren Myneni <haren@us.ibm.com>2006-02-10 01:51:05 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-02-10 08:13:12 -0800
commit9c15e852a524d55ab768cf48c97f5c684f876af2 (patch)
tree897cc70b792652599e7f135e4cb4aeff82a3f2b8 /security
parentafcd024183d8a6eae7e489ce50b2485c5ae4f662 (diff)
downloadlinux-stable-9c15e852a524d55ab768cf48c97f5c684f876af2.tar.gz
linux-stable-9c15e852a524d55ab768cf48c97f5c684f876af2.tar.bz2
linux-stable-9c15e852a524d55ab768cf48c97f5c684f876af2.zip
[PATCH] kexec: fix in free initrd when overlapped with crashkernel region
It is possible that the reserved crashkernel region can be overlapped with initrd since the bootloader sets the initrd location. When the initrd region is freed, the second kernel memory will not be contiguous. The Kexec_load can cause an oops since there is no contiguous memory to write the second kernel or this memory could be used in the first kernel itself and may not be part of the dump. For example, on powerpc, the initrd is located at 36MB and the crashkernel starts at 32MB. The kexec_load caused panic since writing into non-allocated memory (after 36MB). We could see the similar issue even on other archs. One possibility is to move the initrd outside of crashkernel region. But, the initrd region will be freed anyway before the system is up. This patch fixes this issue and frees only regions that are not part of crashkernel memory in case overlaps. Signed-off-by: Haren Myneni <haren@us.ibm.com> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Vivek Goyal <vgoyal@in.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions