From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: pasha.tatashin@soleen.com, tyhicks@linux.microsoft.com,
jmorris@namei.org, catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, anshuman.khandual@arm.com,
rppt@kernel.org, logang@deltatee.com, ardb@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] correct the inside linear map boundaries during hotplug check
Date: Mon, 15 Feb 2021 14:22:36 -0500 [thread overview]
Message-ID: <20210215192237.362706-1-pasha.tatashin@soleen.com> (raw)
v2:
- Added test-by Tyler Hicks
- Addressed comments from Anshuman Khandual: moved check under
IS_ENABLED(CONFIG_RANDOMIZE_BASE), added
WARN_ON(start_linear_pa > end_linear_pa);
Fixes a hotplug error that may occur on systems with CONFIG_RANDOMIZE_BASE
enabled.
v1:
https://lore.kernel.org/lkml/20210213012316.1525419-1-pasha.tatashin@soleen.com
Pavel Tatashin (1):
arm64: mm: correct the inside linear map boundaries during hotplug
check
arch/arm64/mm/mmu.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-02-15 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:22 Pavel Tatashin [this message]
2021-02-15 19:22 ` [PATCH v2 1/1] arm64: mm: correct the inside linear map boundaries during hotplug check Pavel Tatashin
2021-02-15 19:27 ` Ard Biesheuvel
2021-02-15 19:30 ` Pavel Tatashin
2021-02-15 19:34 ` Ard Biesheuvel
2021-02-15 19:51 ` Pavel Tatashin
2021-02-15 22:28 ` Pavel Tatashin
2021-02-16 3:12 ` Anshuman Khandual
2021-02-16 7:36 ` Ard Biesheuvel
2021-02-16 14:34 ` Pavel Tatashin
2021-02-16 2:55 ` Anshuman Khandual
2021-02-16 14:48 ` Pavel Tatashin
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=20210215192237.362706-1-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=rppt@kernel.org \
--cc=tyhicks@linux.microsoft.com \
--cc=will@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).