diff options
author | Magnus Damm <damm@igel.co.jp> | 2009-01-07 18:09:06 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-01-08 08:31:14 -0800 |
commit | 921d58c0e6992f74d3a48180604a298f115d2dee (patch) | |
tree | db3128a5957a0ff95d2bce1166d61050b1b3e494 /fs/romfs | |
parent | 4037014e3fb71e998189374e19ca141c59d15323 (diff) | |
download | linux-3.10-921d58c0e6992f74d3a48180604a298f115d2dee.tar.gz linux-3.10-921d58c0e6992f74d3a48180604a298f115d2dee.tar.bz2 linux-3.10-921d58c0e6992f74d3a48180604a298f115d2dee.zip |
vmcore: remove saved_max_pfn check
Remove the saved_max_pfn check from the /proc/vmcore function
read_from_oldmem(). No need to verify, we should be able to just trust
that "elfcorehdr=" is correctly passed to the crash kernel on the kernel
command line like we do with other parameters.
The read_from_oldmem() function in fs/proc/vmcore.c is quite similar to
read_from_oldmem() in drivers/char/mem.c, but only in the latter it makes
sense to use saved_max_pfn. For oldmem it is used to determine when to
stop reading. For vmcore we already have the elf header info pointing out
the physical memory regions, no need to pass the end-of- old-memory twice.
Removing the saved_max_pfn check from vmcore makes it possible for
architectures to skip oldmem but still support crash dump through vmcore -
without the need for the old saved_max_pfn cruft.
Architectures that want to play safe can do the saved_max_pfn check in
copy_oldmem_page(). Not sure why anyone would want to do that, but that's
even safer than today - the saved_max_pfn check in vmcore removed by this
patch only checks the first page.
Signed-off-by: Magnus Damm <damm@igel.co.jp>
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Acked-by: Simon Horman <horms@verge.net.au>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/romfs')
0 files changed, 0 insertions, 0 deletions