From: "Alastair D'Silva" <alastair@au1.ibm.com>
To: alastair@d-silva.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@linux.ibm.com>, Baoquan He <bhe@redhat.com>,
Wei Yang <richard.weiyang@gmail.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v2 1/3] mm: Trigger bug on if a section is not found in __section_nr
Date: Wed, 26 Jun 2019 16:11:21 +1000 [thread overview]
Message-ID: <20190626061124.16013-2-alastair@au1.ibm.com> (raw)
In-Reply-To: <20190626061124.16013-1-alastair@au1.ibm.com>
From: Alastair D'Silva <alastair@d-silva.org>
If a memory section comes in where the physical address is greater than
that which is managed by the kernel, this function would not trigger the
bug and instead return a bogus section number.
This patch tracks whether the section was actually found, and triggers the
bug if not.
Signed-off-by: Alastair D'Silva <alastair@d-silva.org>
---
drivers/base/memory.c | 18 +++++++++++++++---
mm/sparse.c | 7 ++++++-
2 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index f180427e48f4..9244c122abf1 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -585,13 +585,21 @@ int __weak arch_get_memory_phys_device(unsigned long start_pfn)
struct memory_block *find_memory_block_hinted(struct mem_section *section,
struct memory_block *hint)
{
- int block_id = base_memory_block_id(__section_nr(section));
+ int block_id, section_nr;
struct device *hintdev = hint ? &hint->dev : NULL;
struct device *dev;
+ section_nr = __section_nr(section);
+ if (section_nr < 0) {
+ if (hintdev)
+ put_device(hintdev);
+ return NULL;
+ }
+
+ block_id = base_memory_block_id(section_nr);
dev = subsys_find_device_by_id(&memory_subsys, block_id, hintdev);
- if (hint)
- put_device(&hint->dev);
+ if (hintdev)
+ put_device(hintdev);
if (!dev)
return NULL;
return to_memory_block(dev);
@@ -664,6 +672,10 @@ static int init_memory_block(struct memory_block **memory,
return -ENOMEM;
scn_nr = __section_nr(section);
+
+ if (scn_nr < 0)
+ return scn_nr;
+
mem->start_section_nr =
base_memory_block_id(scn_nr) * sections_per_block;
mem->end_section_nr = mem->start_section_nr + sections_per_block - 1;
diff --git a/mm/sparse.c b/mm/sparse.c
index fd13166949b5..57a1a3d9c1cf 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -113,10 +113,15 @@ int __section_nr(struct mem_section* ms)
continue;
if ((ms >= root) && (ms < (root + SECTIONS_PER_ROOT)))
- break;
+ break;
}
VM_BUG_ON(!root);
+ if (root_nr == NR_SECTION_ROOTS) {
+ VM_BUG_ON(true);
+
+ return -EINVAL;
+ }
return (root_nr * SECTIONS_PER_ROOT) + (ms - root);
}
--
2.21.0
next prev parent reply other threads:[~2019-06-26 6:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 6:11 [PATCH v2 0/3] mm: Cleanup & allow modules to hotplug memory Alastair D'Silva
2019-06-26 6:11 ` Alastair D'Silva [this message]
2019-06-26 6:21 ` [PATCH v2 1/3] mm: Trigger bug on if a section is not found in __section_nr Michal Hocko
2019-06-26 6:27 ` Alastair D'Silva
2019-06-26 6:57 ` Michal Hocko
2019-06-27 0:50 ` Alastair D'Silva
2019-06-27 8:10 ` Michal Hocko
2019-06-28 0:46 ` Alastair D'Silva
2019-07-01 10:46 ` Michal Hocko
2019-07-02 4:13 ` Alastair D'Silva
2019-07-02 6:13 ` Michal Hocko
2019-07-02 6:16 ` Alastair D'Silva
2019-06-28 11:37 ` David Hildenbrand
2019-06-28 11:58 ` Michal Hocko
2019-06-26 6:11 ` [PATCH v2 2/3] mm: don't hide potentially null memmap pointer in sparse_remove_one_section Alastair D'Silva
2019-06-26 6:23 ` Michal Hocko
2019-06-26 6:30 ` Alastair D'Silva
2019-06-26 6:59 ` Michal Hocko
2019-06-28 11:29 ` David Hildenbrand
2019-06-26 6:11 ` [PATCH v2 3/3] mm: Don't manually decrement num_poisoned_pages Alastair D'Silva
2019-06-26 6:24 ` Michal Hocko
2019-06-28 11:29 ` David Hildenbrand
2019-06-26 7:57 ` [PATCH v2 0/3] mm: Cleanup & allow modules to hotplug memory Christoph Hellwig
2019-06-27 0:51 ` Alastair D'Silva
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=20190626061124.16013-2-alastair@au1.ibm.com \
--to=alastair@au1.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alastair@d-silva.org \
--cc=bhe@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=rafael@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=rppt@linux.ibm.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