>Number:         33909
>Category:       bin
>Synopsis:       modload fails with "section .eh_frame ... overlaps section .data"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 03 21:45:00 +0000 2006
>Originator:     Dave Huang
>Release:        NetBSD 3.99.21
>Organization:
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 30 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++
>Environment:
	
	
System: NetBSD yerfable.azeotrope.org 3.99.21 NetBSD 3.99.21 (YERFABLE) #220: Wed Jun 14 16:35:23 CDT 2006 khym@yerfable.azeotrope.org:/usr2/obj.alpha/sys/arch/alpha/compile/YERFABLE alpha
Architecture: alpha
Machine: alpha
>Description:
	modload fails to load any lkms, even ones that worked fine in
the past. I suspect this started happening after binutils was updated
in early February.

	On amd64-current with Feb 19 kernel and userland:
ld: section .eh_frame [ffffffff80651768 -> ffffffff8065261f] overlaps section .data [ffffffff806525c0 -> ffffffff80652a27]
modload: can't link `/usr/lkm/udf.o' creating `/usr/lkm/udf' bound to 0xffffffff 8064c000

	On alpha-current with June 14 kernel and userland:
ld: section .eh_frame [fffffe000c5a4750 -> fffffe000c5a47f7] overlaps section .data [fffffe000c5a47f0 -> fffffe000c5a48c7]
modload: can't link `nullfs.o' creating `nullfs' bound to 0xfffffe000c5a4000

>How-To-Repeat:
	Attempt to load an LKM with modload. E.g., modload /usr/lkm/nullfs.o
>Fix:
	Modifying modload to call ld with the --no-check-sections flag
seems to work, but it seems that the way LKMs are built should be
changed so that the flag isn't required.

>Unformatted: