[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <159675712611.3192.9276107273934429682.tip-bot2@tip-bot2>
Date: Thu, 06 Aug 2020 23:38:46 -0000
From: "tip-bot2 for Lianbo Jiang" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: Lianbo Jiang <lijiang@...hat.com>, Ingo Molnar <mingo@...nel.org>,
Dave Young <dyoung@...hat.com>, x86 <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: [tip: x86/urgent] x86/crash: Correct the address boundary of function
parameters
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: a3e1c3bb24e2ff2927af5e30c2bebe669bb84196
Gitweb: https://git.kernel.org/tip/a3e1c3bb24e2ff2927af5e30c2bebe669bb84196
Author: Lianbo Jiang <lijiang@...hat.com>
AuthorDate: Tue, 04 Aug 2020 12:49:31 +08:00
Committer: Ingo Molnar <mingo@...nel.org>
CommitterDate: Fri, 07 Aug 2020 01:32:00 +02:00
x86/crash: Correct the address boundary of function parameters
Let's carefully handle the boundary of the function parameter to make
sure that the arguments passed doesn't exceed the address range.
Signed-off-by: Lianbo Jiang <lijiang@...hat.com>
Signed-off-by: Ingo Molnar <mingo@...nel.org>
Acked-by: Dave Young <dyoung@...hat.com>
Link: https://lore.kernel.org/r/20200804044933.1973-2-lijiang@redhat.com
---
arch/x86/kernel/crash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c
index fd87b59..a8f3af2 100644
--- a/arch/x86/kernel/crash.c
+++ b/arch/x86/kernel/crash.c
@@ -230,7 +230,7 @@ static int elf_header_exclude_ranges(struct crash_mem *cmem)
int ret = 0;
/* Exclude the low 1M because it is always reserved */
- ret = crash_exclude_mem_range(cmem, 0, 1<<20);
+ ret = crash_exclude_mem_range(cmem, 0, (1<<20)-1);
if (ret)
return ret;
Powered by blists - more mailing lists