From: "tip-bot2 for Lianbo Jiang" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Lianbo Jiang <lijiang@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Dave Young <dyoung@redhat.com>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/urgent] x86/crash: Correct the address boundary of function parameters
Date: Thu, 06 Aug 2020 17:10:07 -0000 [thread overview]
Message-ID: <159673380758.3192.12299066068844130724.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200804044933.1973-2-lijiang@redhat.com>
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 5b89a35f8c11a7846b06ac729d7de72044f7fc60
Gitweb: https://git.kernel.org/tip/5b89a35f8c11a7846b06ac729d7de72044f7fc60
Author: Lianbo Jiang <lijiang@redhat.com>
AuthorDate: Tue, 04 Aug 2020 12:49:31 +08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Thu, 06 Aug 2020 15:25:58 +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@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Dave Young <dyoung@redhat.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;
next prev parent reply other threads:[~2020-08-06 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 4:49 [PATCH 0/3] x86/kexec_file: Fix some corners bugs and improve the crash_exclude_mem_range() Lianbo Jiang
2020-08-04 4:49 ` [PATCH 1/3] x86/crash: Correct the address boundary of function parameters Lianbo Jiang
2020-08-06 17:10 ` tip-bot2 for Lianbo Jiang [this message]
2020-08-06 23:38 ` [tip: x86/urgent] " tip-bot2 for Lianbo Jiang
2020-08-04 4:49 ` [PATCH 2/3] kexec: Improve the crash_exclude_mem_range() to handle the overlapping ranges Lianbo Jiang
2020-08-06 17:10 ` [tip: x86/urgent] kexec: Improve & fix crash_exclude_mem_range() to handle " tip-bot2 for Lianbo Jiang
2020-08-06 23:38 ` tip-bot2 for Lianbo Jiang
2020-08-04 4:49 ` [PATCH 3/3] kexec_file: correctly output debugging information for the PT_LOAD elf header Lianbo Jiang
2020-08-06 17:10 ` [tip: x86/urgent] kexec_file: Correctly output debugging information for the PT_LOAD ELF header tip-bot2 for Lianbo Jiang
2020-08-06 23:38 ` tip-bot2 for Lianbo Jiang
2020-08-05 6:36 ` [PATCH 0/3] x86/kexec_file: Fix some corners bugs and improve the crash_exclude_mem_range() Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=159673380758.3192.12299066068844130724.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=dyoung@redhat.com \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).