forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Labels
[ARCH] hexagonThis bug impacts ARCH=hexagonThis bug impacts ARCH=hexagon[BUG] linux-nextThis is an issue only seen in linux-nextThis is an issue only seen in linux-next[FIXED][LINUX] development cycleThis bug was only present and fixed in a -next or -rc cycleThis bug was only present and fixed in a -next or -rc cycle
Description
Pointed out by our CI: https://github.com/ClangBuiltLinux/continuous-integration2/runs/2628252183?check_suite_focus=true
$ tuxmake -a hexagon -r podman -t llvm-nightly -w ccache
...
ld.lld: error: undefined symbol: __irqentry_text_start
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
ld.lld: error: undefined symbol: __irqentry_text_end
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
ld.lld: error: undefined symbol: __softirqentry_text_start
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
ld.lld: error: undefined symbol: __softirqentry_text_end
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
>>> referenced by stackdepot.c
>>> stackdepot.o:(filter_irq_stacks) in archive lib/built-in.a
...
CONFIG_STACKDEPOT is now selected, which reveals that Hexagon has never handled IRQENTRY_TEXT and SOFTIRQENTRY_TEXT, which is necessary for CONFIG_STACKDEPOT after https://git.kernel.org/linus/505a0ef15f96c6c43ec719c9fc1833d98957bb39.
Patch submitted: https://lore.kernel.org/r/20210521011239.1332345-2-nathan@kernel.org/
Metadata
Metadata
Assignees
Labels
[ARCH] hexagonThis bug impacts ARCH=hexagonThis bug impacts ARCH=hexagon[BUG] linux-nextThis is an issue only seen in linux-nextThis is an issue only seen in linux-next[FIXED][LINUX] development cycleThis bug was only present and fixed in a -next or -rc cycleThis bug was only present and fixed in a -next or -rc cycle