linux-kernel - RE: [PATCH] mm: Check if section present during memory block (un)registering

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F32AECDFD@ORSMSX114.amr.corp.intel.com>
Date:	Tue, 25 Aug 2015 23:24:22 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Yinghai Lu <yinghai@...nel.org>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] mm: Check if section present during memory block
 (un)registering

> It appears this should be backported into -stable kernels, yes?  Do you
> know which kernel versions need the fix?

For my setup the problem is first seen after:

commit bdee237c0343 " x86: mm: Use 2GB memory block size on large memory x86-64 systems"

which appeared in v3.19 and forced a 2GB memory block size.  But it could happen on older
systems depending on the block size picked based on the alignment of max_pfn.

Looking further back (to v3.15) ... we used a fixed MIN_MEMORY_BLOCK_SIZE for
all systems prior to 

commit 982792c782ef "x86, mm: probe memory block size for generic x86 64bit"

So maybe:

Cc: stable@...nel.org #v3.15

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/