linux-kernel - [PATCH 0/2] fix a kernel oops in reading sysfs valid

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20170126214415.4509-1-toshi.kani@hpe.com>
Date:   Thu, 26 Jan 2017 14:44:13 -0700
From:   Toshi Kani <toshi.kani@....com>
To:     akpm@...ux-foundation.org, gregkh@...uxfoundation.org
Cc:     linux-mm@...ck.org, zhenzhang.zhang@...wei.com,
        arbab@...ux.vnet.ibm.com, dan.j.williams@...el.com,
        abanman@....com, rientjes@...gle.com, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] fix a kernel oops in reading sysfs valid_zones

A sysfs memory file is created for each 128MiB or 2GiB of a memory
block on x86. [1]  When the start address of a memory block is not
backed by struct page, i.e. memory range is not aligned by the memory
block size, reading its valid_zones attribute file leads to a kernel
oops.  This patch-set fixes this issue.

Patch 1 first fixes an issue in test_pages_in_a_zone() that it does
not test the start section.

Patch 2 then fixes the kernel oops by extending test_pages_in_a_zone()
to return valid [start, end).

[1] 2GB when the system has 64GB or larger memory.

---
Toshi Kani (2):
 1/2 mm/memory_hotplug.c: check start_pfn in test_pages_in_a_zone() 
 2/2 base/memory, hotplug: fix a kernel oops in show_valid_zones()

---
 drivers/base/memory.c          | 12 ++++++------
 include/linux/memory_hotplug.h |  3 ++-
 mm/memory_hotplug.c            | 28 +++++++++++++++++++++-------
 3 files changed, 29 insertions(+), 14 deletions(-)