kernelci / kernelci/kernelci-core
Decode kernel kernel oopses/warns
- Dominant language
- Python
- Stars
- 120
- Forks
- 107
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 21
Description
In order to improve the immediate usability of kernel logs with backtraces in it is helpful to demangle the addresses printed to show actual code lines. There is a tool in the kernel to do this which is run like so:
CROSS_COMPILE=aarch64-none-linux-gnu- ./scripts/decode_stacktrace.sh vlinux < raw.log > parsed.log
(note that it needs vmlinux which we don't currently save, and a toolchain). The simplest thing would just be to run all logs through the script after they've been posted, it'd be a bit expensive o fire up containers for it though so e might want to be smarter about it.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading scripts/decode_stacktrace.sh and the issue's example command, then inspect how posted kernel logs and vmlinux files are currently handled. Define how logs would be processed when the required vmlinux image and toolchain are available, including whether container startup is needed; done means backtrace addresses are rendered as code lines in the resulting logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- operating-systems, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100