From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422857AbXCWMzm (ORCPT ); Fri, 23 Mar 2007 08:55:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422862AbXCWMzm (ORCPT ); Fri, 23 Mar 2007 08:55:42 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:48576 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422857AbXCWMzl (ORCPT ); Fri, 23 Mar 2007 08:55:41 -0400 X-Greylist: delayed 124677 seconds by postgrey-1.27 at vger.kernel.org; Fri, 23 Mar 2007 08:55:40 EDT Date: Fri, 23 Mar 2007 21:54:29 +0900 From: Yasunori Goto To: Sam Ravnborg Subject: Re: 2.6.21-rc4-mm1 + 3 hot-fixes -- WARNING: could not find versions for .tmp_versions/built-in.mod Cc: Miles Lane , Andrew Morton , LKML In-Reply-To: <20070320212705.GB13349@uranus.ravnborg.org> References: <20070320212705.GB13349@uranus.ravnborg.org> X-Mailer-Plugin: BkASPil for Becky!2 Ver.2.068 Message-Id: <20070323214418.3F04.Y-GOTO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.27 [ja] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello. > > WARNING: mm/built-in.o - Section mismatch: reference to > > .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at > > offset 0x15c8f) and '__section_nr' > I took a look at this one. > You have SPARSEMEM enabled in your config. > And then I see that in sparse.c we call alloc_bootmem_node() > from a function I thought should be marked __devinit (it > is used by memory_hotplug.c). > But I am not familiar enough to judge if __alloc_bootmen_node > are marked correct with __init or __devinit (to say > this is used in the HOTPLUG case) is more correct. > Anyone? > > > WARNING: mm/built-in.o - Section mismatch: reference to > > .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at > > offset 0x15d02) and '__section_nr' > Same as above.... Memory hotplug code has __meminit for its purpose. But, I suspect that many other places of memory hotplug code may have same issue. I will chase them. BTW, does -mm code checks more strict than stock kernel? I can't see these warnings in 2.6.21-rc4..... Bye. -- Yasunori Goto