linux-kernel - [stable 3.0 revert request] x86-32, mm: Remove reference to resume_map_numa

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: <515EB8B6.3070900@suse.cz>
Date:	Fri, 05 Apr 2013 13:42:46 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	stable <stable@...r.kernel.org>
CC:	hpa@...ux.intel.com, Mel Gorman <mgorman@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Hansen <dave@...ux.vnet.ibm.com>
Subject: [stable 3.0 revert request] x86-32, mm: Remove reference to resume_map_numa_kva()

Hi,

in 3.0.67 there is this commit:
commit dbb694e810c87e7e1760527a783437f26ac5a547
Author: H. Peter Anvin <hpa@...ux.intel.com>
Date:   Thu Jan 31 13:53:10 2013 -0800

    x86-32, mm: Remove reference to resume_map_numa_kva()

    commit bb112aec5ee41427e9b9726e3d57b896709598ed upstream.

    Remove reference to removed function resume_map_numa_kva().



But it depends on f03574f2 (which was applied to 3.2, 3.4, 3.7 and 3.8
stable trees, but not to 3.0). Now, when f03574f2 is not there, resume
from suspend dies terrible death on 32-bit:
Enabling non-boot CPUs ...
------------[ cut here ]------------
kernel BUG at mm/slab.c:532!
invalid opcode: 0000 [#1] SMP


In 3.0, we need either f03574f2:
commit f03574f2d5b2d6229dcdf2d322848065f72953c7
Author: Dave Hansen <dave@...ux.vnet.ibm.com>
Date:   Wed Jan 30 16:56:16 2013 -0800

    x86-32, mm: Rip out x86_32 NUMA remapping code

or revert the commit above...

thanks,
-- 
js
suse labs
--
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/