On Tue, May 3, 2016 at 3:52 PM, Russell King <rmk at arm.linux.org.uk> wrote:
> The memory range end is inclusive, not exclusive (see x86). We should
> not be adding one to the value parsed from the /proc/iomem resources.
>
> Signed-off-by: Russell King <rmk at arm.linux.org.uk>
Reviewed-by: Pratyush Anand <panand at redhat.com>
I think, this also need to be fixed for ARM64 patches. +Geoff
> ---
> kexec/arch/arm/kexec-arm.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kexec/arch/arm/kexec-arm.c b/kexec/arch/arm/kexec-arm.c
> index 4e90e69..e47fc00 100644
> --- a/kexec/arch/arm/kexec-arm.c
> +++ b/kexec/arch/arm/kexec-arm.c
> @@ -51,7 +51,6 @@ int get_memory_ranges(struct memory_range **range, int *ranges,
> if (count != 2)
> continue;
> str = line + consumed;
> - end = end + 1;
>
> if (memcmp(str, "System RAM\n", 11) == 0) {
> type = RANGE_RAM;
> --
> 1.9.1
>
