linux/arch/i386/boot/compressed
Al Viro 2a3d4f1f1f [PATCH] __crc_... is intended to be absolute
i386 boot/compressed/relocs checks for absolute symbols and warns about
unexpected ones.  If you build with modversions, you get ~2500 warnings
about __crc_<symbol>.  These suckers are really absolute symbols - we
do _not_ want to modify them on relocation.

They are generated by genksyms - EXPORT_... generates a weak alias, then
genksyms produces an ld script with __crc_<symbol> = <checksum> and it's
fed to ld to produce the final object file.  Their only use is to match
kernel and module at modprobe time; they _must_ be absolute.

boot/compressed/relocs has a whitelist of known absolute symbols, but
it doesn't know about __crc_... stuff.  As the result, we get shitloads
of false positives on any ld(1) version.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-02-01 16:17:06 -08:00
..
.gitignore [PATCH] Add .gitignore file for relocs in arch/i386 2006-12-30 10:55:55 -08:00
head.S [PATCH] Fix insta-reboot with "i386: Relocatable kernel support" 2007-01-02 13:44:11 -08:00
Makefile [PATCH] i386: Warn upon absolute relocations being present 2006-12-07 02:14:04 +01:00
misc.c [PATCH] x86-64: Fix numaq build error 2006-12-07 02:14:13 +01:00
relocs.c [PATCH] __crc_... is intended to be absolute 2007-02-01 16:17:06 -08:00
vmlinux.lds [PATCH] i386: Relocatable kernel support 2006-12-07 02:14:04 +01:00
vmlinux.scr [PATCH] i386: Relocatable kernel support 2006-12-07 02:14:04 +01:00