| commit | 68e6fad488ef21335529c65ca6c88c38be50cd3a | |
| author | Russell King <rmk+kernel@arm.linux.org.uk> | |
| Tue, 11 Jan 2011 19:57:14 +0000 (11 19:57 +0000) | ||
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | |
| Wed, 23 Feb 2011 17:24:14 +0000 (23 17:24 +0000) | ||
| tree | a9ca2d10ee703bbc4ccff79385bd0ee95dcbc29b | treesnapshot (tar.gz zip) |
| parent | a65d29225ed884456f3d34dcefd3a18df24af03b | commitdiff |
ARM: improve module relocation fixup diagnostics
Current diagnostics are rather poor when things go wrong:
ipv6: relocation out of range, section 2 reloc 0 sym 'snmp_mib_free'
Let's include a little more information about the problem:
ipv6: section 2 reloc 0 sym 'snmp_mib_free': relocation 28 out of range (0xbf0000a4 -> 0xc11b4858)
so that we show exactly what the problem is - not only what type of
relocation but also the offending address range too.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Current diagnostics are rather poor when things go wrong:
ipv6: relocation out of range, section 2 reloc 0 sym 'snmp_mib_free'
Let's include a little more information about the problem:
ipv6: section 2 reloc 0 sym 'snmp_mib_free': relocation 28 out of range (0xbf0000a4 -> 0xc11b4858)
so that we show exactly what the problem is - not only what type of
relocation but also the offending address range too.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
| arch/arm/kernel/module.c | diffblobblamehistory |