On Mon 2021-05-10 17:38:32, Stephen Boyd wrote: > This series adds the kernel's build ID[1] to the stacktrace header > printed in oops messages, warnings, etc. and the build ID for any module > that appears in the stacktrace after the module name. The goal is to > make the stacktrace more self-contained and descriptive by including the > relevant build IDs in the kernel logs when something goes wrong. This > can be used by post processing tools like script/decode_stacktrace.sh > and kernel developers to easily locate the debug info associated with a > kernel crash and line up what line and file things started falling apart > at. The entire series looks good to me. I reviewed carefully only the 5th patch touching printk/kallsyms/module code. I just scanned over the other patches touching kernel code and did not notice any obvious problem. I did not check the changes in decode_stacktrace.sh at all. I tried to get stacktraces on x86_64 and it worked as expected. Best Regards, Petr _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
