From: "Alastair D'Silva" <alastair@au1.ibm.com>
To: alastair@d-silva.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
David Hildenbrand <david@redhat.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/1] Add bounds check for Hotplugged memory
Date: Tue, 1 Oct 2019 10:46:14 +1000 [thread overview]
Message-ID: <20191001004617.7536-1-alastair@au1.ibm.com> (raw)
From: Alastair D'Silva <alastair@d-silva.org>
This series adds bounds checks for hotplugged memory, ensuring that
it is within the physically addressable range (for platforms that
define MAX_(POSSIBLE_)PHYSMEM_BITS.
This allows for early failure, rather than attempting to access
bogus section numbers.
Changelog:
V7:
- Cast PFN_PHYS as u64 since it's type is platform dependant
V6:
- Fix printf formats
V5:
- Factor out calculation into max_allowed var
- Declare unchanging vars as const
- Use PFN_PHYS macro instead of shifting by PAGE_SHIFT
V4:
- Relocate call to __add_pages
- Add a warning when the addressable check fails
V3:
- Perform the addressable check before we take the hotplug lock
V2:
- Don't use MAX_POSSIBLE_PHYSMEM_BITS as it's wider that what
may be available
Alastair D'Silva (1):
memory_hotplug: Add a bounds check to __add_pages
mm/memory_hotplug.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
2.21.0
next reply other threads:[~2019-10-01 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 0:46 Alastair D'Silva [this message]
2019-10-01 0:46 ` [PATCH v7 1/1] memory_hotplug: Add a bounds check to __add_pages Alastair D'Silva
2019-10-01 9:49 ` David Hildenbrand
2019-10-02 22:14 ` Andrew Morton
2019-10-02 23:27 ` Alastair D'Silva
2019-10-04 12:08 ` Michal Hocko
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=20191001004617.7536-1-alastair@au1.ibm.com \
--to=alastair@au1.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alastair@d-silva.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
/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).