Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] kconfig: syntax error due to insufficient indentation in help text --
commit d0f9200d03ebaf0ef39b9f78a15ab259102ed7e8 Author: Jan Sebastian Götte <[email protected]> kexec: Expose the crash memaction bitmap in debugfs This commit adds debugfs support to expose the crash memaction bitmap by creating "regions" and "bitmap" files under /sys/kernel/debug/crash_memaction/. The feature is guarded by the new CONFIG_CRASH_MEMACTION_DEBUGFS option. > diff --git a/kernel/Kconfig.kexec b/kernel/Kconfig.kexec > index 3cdc8d459ac05..b5380e16bfafb 100644 > --- a/kernel/Kconfig.kexec > +++ b/kernel/Kconfig.kexec > @@ -204,4 +204,18 @@ config CRASH_MEMACTION [ ... ] > +config CRASH_MEMACTION_DEBUGFS > + bool "Expose the crash memaction bitmap in debugfs" > + depends on CRASH_MEMACTION && DEBUG_FS > + help > + Allow reading the live crash_memaction bitmap through > + /sys/kernel/debug/crash_memaction/. The bitmap is used when [Severity: Low] Does this indentation break the Kconfig help block? The first line of the help text is indented with 1 tab and 2 spaces (which is equivalent to 10 spaces in Kconfig), but this line starts with only 6 spaces. The Kconfig lexer terminates a help block when it encounters an indentation level lower than the block's first line. This could cause the parser to interpret the rest of the text as an invalid Kconfig directive, potentially resulting in a syntax error and build failure during make config. > + CRASH_MEMACTION is set and when a crash_memaction cmdline param is > present > + to tell an eventual kdump kernel about the use of certain memory pages. > + > + Note that this is a debug interface only that gives no guarantees > + whatsoever on memory consistency. > + > + If unsure, say N. > + > endmenu -- Sashiko AI review · https://sashiko.dev/#/patchset/20260928-crash-memaction-upstream-20260921-v3-0-e511e9ee2...@jaseg.de?part=12
