From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Ravnborg Subject: Re: modpost warning question Date: Wed, 25 Jul 2007 09:27:12 +0200 Message-ID: <20070725072712.GB24093@uranus.ravnborg.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Andy Fleming , Jeff Garzik , netdev@vger.kernel.org To: Kumar Gala Return-path: Received: from pasmtpa.tele.dk ([80.160.77.114]:53124 "EHLO pasmtpA.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763196AbXGYHZ6 (ORCPT ); Wed, 25 Jul 2007 03:25:58 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, Jul 25, 2007 at 02:14:12AM -0500, Kumar Gala wrote: > I'm seeing the following warning: > > WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to > .exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init') > > I don't understand why its not ok to access .exit.text from .init.text Several architectures discards .exit.text in the final linker script (arch/$(ARCH)/kernel/vmlinux.lds.S So any references to .exit.text will when a module is build-in result in a linker error because ld will flag it as an error when we reference a symbol in a discarded section. For the popular architectures (i386,x86_64) we discard .exit.text at runtime so here we do not see the error from ld (sadly). Sam