summaryrefslogtreecommitdiffstats
path: root/security/tomoyo
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2011-11-07 19:04:36 +0000
committerRussell King <rmk+kernel@arm.linux.org.uk>2011-11-07 19:04:36 +0000
commitabf015f04614a3a7da43d35b55edc90189af4e6a (patch)
treec5ec02b60b9fc84c4ac6c5ccaf279722b8978f95 /security/tomoyo
parent31555213f03bca37d2c02e10946296052f4ecfcd (diff)
downloadlinux-abf015f04614a3a7da43d35b55edc90189af4e6a.tar.gz
linux-abf015f04614a3a7da43d35b55edc90189af4e6a.tar.bz2
linux-abf015f04614a3a7da43d35b55edc90189af4e6a.zip
Revert "ARM: 7098/1: kdump: copy kernel relocation code at the kexec prepare stage"
This reverts commit 2b034922af2caa19df86f0c502e76cb6f6e910f9. Will Deacon reports: This is causing kexec to fail. The symptoms are that the .init.text section is not loaded as part of the new kernel image, so when we try to do the SMP/UP fixups we hit a whole sea of poison left there by the previous kernel. So my guess is that machine_kexec_prepare *is* too early for preparing the reboot_code_buffer and, unless anybody has a good reason not to, I'd like to revert the patch causing these problems. Reported-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'security/tomoyo')
0 files changed, 0 insertions, 0 deletions