lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 16 Sep 2019 16:05:38 +1000 From: "Alastair D'Silva" <alastair@....ibm.com> To: alastair@...ilva.org Cc: Andrew Morton <akpm@...ux-foundation.org>, David Hildenbrand <david@...hat.com>, Oscar Salvador <osalvador@...e.com>, Michal Hocko <mhocko@...e.com>, Pavel Tatashin <pasha.tatashin@...een.com>, Dan Williams <dan.j.williams@...el.com>, Wei Yang <richard.weiyang@...il.com>, Qian Cai <cai@....pw>, Jason Gunthorpe <jgg@...pe.ca>, Logan Gunthorpe <logang@...tatee.com>, Ira Weiny <ira.weiny@...el.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: [PATCH v2 0/2] Add bounds check for Hotplugged memory From: Alastair D'Silva <alastair@...ilva.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: V2: - Don't use MAX_POSSIBLE_PHYSMEM_BITS as it's wider that what may be available Alastair D'Silva (2): memory_hotplug: Add a bounds check to check_hotplug_memory_range() mm: Add a bounds check in devm_memremap_pages() include/linux/memory_hotplug.h | 1 + mm/memory_hotplug.c | 13 ++++++++++++- mm/memremap.c | 8 ++++++++ 3 files changed, 21 insertions(+), 1 deletion(-) -- 2.21.0
Powered by blists - more mailing lists