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: Fri, 20 Jul 2007 22:39:09 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: Paul Mundt <lethal@...ux-sh.org> Cc: mel@...net.ie, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mm: Fix memory hotplug oops from ZONE_MOVABLE changes. On Fri, 20 Jul 2007 20:42:46 +0900 Paul Mundt <lethal@...ux-sh.org> wrote: > > I expect that the memory gets added to the same zone as historically but > > when ZONE_MOVABLE is set, you'll see a situation where zones are overlapping > > after memory hot-add. i.e. Before memory hot-add, you'd see > > > > DDDDMM > > > > for ZONE_DMA and ZONE_MOVABLE and after hotadd, you'd see something like > > > > DDDDMMDDDD > > As similar case, I hear powerpc has followig memory layout (1)(1)(0)(0)(0)(1)(1)(1) # (0) is node 0, (1) is node 1. all zones are ZONE_DMA. So zone is overlapped without memory hotplug. But I agree we have to take care of this kind of corner cases. Thanks, -Kame - 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