diff options
| author | Zhang Yanfei <zhangyanfei@cn.fujitsu.com> | 2013-02-26 18:12:54 +0800 |
|---|---|---|
| committer | Simon Horman <horms@verge.net.au> | 2013-03-05 10:42:40 +0900 |
| commit | 47cfdc16a9565262a32c4a32a23387068e969d2a (patch) | |
| tree | c32234af4874b5309cb15f2dfcd2f619f5726c7b | |
| parent | 28d413ad1627d76acc8f0df3fdb91a3c8d14d92f (diff) | |
| download | kexec-tools-47cfdc16a9565262a32c4a32a23387068e969d2a.tar.gz | |
kexec,x86: Use macro CRASH_MAX_MEMMAP_NR for clarification
For the allocation, using CRASH_MAX_MEMMAP_NR instead of KEXEC_MAX_SEGMENTS + 1
seems more understandable.
Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
[horms@verge.net.au: Applied by hand due to conflict]
Signed-off-by: Simon Horman <horms@verge.net.au>
| -rw-r--r-- | kexec/arch/i386/crashdump-x86.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kexec/arch/i386/crashdump-x86.c b/kexec/arch/i386/crashdump-x86.c index 83bff5ef..6e447413 100644 --- a/kexec/arch/i386/crashdump-x86.c +++ b/kexec/arch/i386/crashdump-x86.c @@ -981,7 +981,7 @@ int load_crashdump_segments(struct kexec_info *info, char* mod_cmdline, return -1; /* Memory regions which panic kernel can safely use to boot into */ - sz = (sizeof(struct memory_range) * (KEXEC_MAX_SEGMENTS + 1)); + sz = (sizeof(struct memory_range) * CRASH_MAX_MEMMAP_NR); memmap_p = xmalloc(sz); memset(memmap_p, 0, sz); add_memmap(memmap_p, info->backup_src_start, info->backup_src_size); |