| 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
| ||
|
Message-Id: <1409C32B-61A8-49D1-BF64-1CFAA5F8B93B@kernel.crashing.org> Date: Wed, 25 Jul 2007 02:49:14 -0500 From: Kumar Gala <galak@...nel.crashing.org> To: Sam Ravnborg <sam@...nborg.org> Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org, Andy Fleming <afleming@...escale.com>, Jeff Garzik <jeff@...zik.org>, netdev@...r.kernel.org Subject: Re: modpost warning question On Jul 25, 2007, at 2:27 AM, Sam Ravnborg wrote: > 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). Fair point, wondering what we do with .exit on PPC, another thing for the list :) - k - 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