diff options
author | Tejun Heo <tj@kernel.org> | 2009-05-26 14:42:40 +0900 |
---|---|---|
committer | H. Peter Anvin <hpa@zytor.com> | 2009-05-25 22:52:49 -0700 |
commit | 46176b4f6bac19454b7b5c35f68594b85850a600 (patch) | |
tree | c67571802f614aa361726d513e9a8fcaee603fb1 /drivers/pnp | |
parent | 71c9d8b68b299bef614afc7907393564a9f1476f (diff) | |
download | linux-46176b4f6bac19454b7b5c35f68594b85850a600.tar.bz2 |
x86, relocs: ignore R_386_NONE in kernel relocation entries
For relocatable 32bit kernels, boot/compressed/relocs.c processes
relocation entries in the kernel image and appends it to the kernel
image such that boot/compressed/head_32.S can relocate the kernel.
The kernel image is one statically linked object and only uses two
relocation types - R_386_PC32 and R_386_32, of the two only the latter
needs massaging during kernel relocation and thus handled by relocs.
R_386_PC32 is ignored and all other relocation types are considered
error.
When the target of a relocation resides in a discarded section,
binutils doesn't throw away the relocation record but nullifies it by
changing it to R_386_NONE, which unfortunately makes relocs fail.
The problem was triggered by yet out-of-tree x86 stack unwind patches
but given the binutils behavior, ignoring R_386_NONE is the right
thing to do.
The problem has been tracked down to binutils behavior by Jan Beulich.
[ Impact: fix build with certain binutils by ignoring R_386_NONE ]
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Jan Beulich <JBeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>
LKML-Reference: <4A1B8150.40702@kernel.org>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Diffstat (limited to 'drivers/pnp')
0 files changed, 0 insertions, 0 deletions