| 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: Sun, 26 May 2013 07:58:42 -0400 From: KOSAKI Motohiro <kosaki.motohiro@...il.com> To: Michal Hocko <mhocko@...e.cz> Cc: Wanpeng Li <liwanp@...ux.vnet.ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, David Rientjes <rientjes@...gle.com>, Jiang Liu <jiang.liu@...wei.com>, Tang Chen <tangchen@...fujitsu.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org Subject: Re: [patch v2 3/6] mm/memory_hotplug: Disable memory hotremove for 32bit >> As KOSAKI Motohiro mentioned, memory hotplug don't support 32bit since >> it was born, > > Why? any reference? This reasoning is really weak. I have no seen any highmem support in memory hotplug code and I don't think this patch fixes all 32bit highmem issue. If anybody are interesting to support it, it is good thing. But in fact, _now_ it is broken when enable HIGHMEM. So, I just want to mark broken until someone want to support highmem and verify overall. And, yes, this patch is no good. Kconfig doesn't describe why disable when highmem. So, depends on 64BIT || !HIGHMEM || BROKEN maybe clear documentation more. -- 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/
Powered by blists - more mailing lists