Linux 6.18 Adding New Option For More Detailed Bug Reporting But Cost Of Greater Memory
([Linux Kernel] 3 Hours Ago
CONFIG_DEBUG_BUGVERBOSE_DETAILED)
- Reference: 0001596124
- News link: https://www.phoronix.com/news/Linux-6.18-Verbose-Bug-On
- Source link:
Among the big flow of pull requests today for this first day of the Linux 6.19 merge window are some core kernel bug handling improvements.
With the batch of pull requests sent in this morning by Ingo Molnar are some core kernel bug handling infrastructure improvements. In addition to improving the Linux kernel's WARN() functionality, there is a new CONFIG_DEBUG_BUGVERBOSE_DETAILED Kconfig option being added.
As implied by the name, CONFIG_DEBUG_BUGVERBOSE_DETAILED allows for more detailed/verbose bug reporting. In particular, DEBUG_BUGVERBOSE_DETAILED allows for more informative reports from the WARN_ON() (and WARN_ON_ONCE()) usage. The kernel's WARN_ON() macro is used for debugging and error checking when the passed condition evaluates to true. Enabling this option will now include the condition string of the warning in addition to the file name and line number.
These more detailed debug messages aren't enabled by default since it comes with a cost of around 100K of memory.
That's the main bug reporting improvement highlight of [1]this pull request .
[1] https://lore.kernel.org/lkml/aS1_wFqXNmDh84jJ@gmail.com/
With the batch of pull requests sent in this morning by Ingo Molnar are some core kernel bug handling infrastructure improvements. In addition to improving the Linux kernel's WARN() functionality, there is a new CONFIG_DEBUG_BUGVERBOSE_DETAILED Kconfig option being added.
As implied by the name, CONFIG_DEBUG_BUGVERBOSE_DETAILED allows for more detailed/verbose bug reporting. In particular, DEBUG_BUGVERBOSE_DETAILED allows for more informative reports from the WARN_ON() (and WARN_ON_ONCE()) usage. The kernel's WARN_ON() macro is used for debugging and error checking when the passed condition evaluates to true. Enabling this option will now include the condition string of the warning in addition to the file name and line number.
These more detailed debug messages aren't enabled by default since it comes with a cost of around 100K of memory.
That's the main bug reporting improvement highlight of [1]this pull request .
[1] https://lore.kernel.org/lkml/aS1_wFqXNmDh84jJ@gmail.com/