From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161510AbXBHHuK (ORCPT ); Thu, 8 Feb 2007 02:50:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161451AbXBHHuK (ORCPT ); Thu, 8 Feb 2007 02:50:10 -0500 Received: from ns2.suse.de ([195.135.220.15]:49370 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161510AbXBHHuJ (ORCPT ); Thu, 8 Feb 2007 02:50:09 -0500 From: Andi Kleen To: KAMEZAWA Hiroyuki Subject: Re: [BUG][PATCH] fix mempolcy's check on a system with memory-less-node take2 Date: Thu, 8 Feb 2007 08:49:41 +0100 User-Agent: KMail/1.9.5 Cc: LKML , clameter@sgi.com, Andrew Morton , GOTO References: <20070208110606.ebf668d3.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20070208110606.ebf668d3.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702080849.42167.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > This panic(hang) was found by a numa test-set on a system with 3 nodes, where > node(2) was memory-less-node. I still think it's the wrong fix -- just get rid of the memory less node. I expect you'll likely run into more problems with that setup anyways. > static struct mempolicy *mpol_new(int mode, nodemask_t *nodes) > { > struct mempolicy *policy; > + void *val; Using void * here is nasty when it's a zonelist pointer. -Andi