From: Linus Torvalds Date: Mon, 4 Aug 2025 17:54:36 +0000 (-0700) Subject: Merge tag 'printk-for-6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/printk... X-Git-Tag: io_uring-6.17-20250815~48 X-Git-Url: https://git.kernel.dk/?a=commitdiff_plain;h=35a813e010b99894bb4706c56c16a580bf7959c2;p=linux-block.git Merge tag 'printk-for-6.17' of git://git./linux/kernel/git/printk/linux Pull printk updates from Petr Mladek: - Add new "hash_pointers=[auto|always|never]" boot parameter to force the hashing even with "slab_debug" enabled - Allow to stop CPU, after losing nbcon console ownership during panic(), even without proper NMI - Allow to use the printk kthread immediately even for the 1st registered nbcon - Compiler warning removal * tag 'printk-for-6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux: printk: nbcon: Allow reacquire during panic printk: Allow to use the printk kthread immediately even for 1st nbcon slab: Decouple slab_debug and no_hash_pointers vsprintf: Use __diag macros to disable '-Wsuggest-attribute=format' compiler-gcc.h: Introduce __diag_GCC_all --- 35a813e010b99894bb4706c56c16a580bf7959c2 diff --cc Documentation/admin-guide/kernel-parameters.txt index c1a5cd991f2e,0dd5cd17e87e..747a55abf494 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@@ -6641,9 -6488,13 +6651,13 @@@ slab_debug can create guard zones around objects and may poison objects when not in use. Also tracks the last alloc / free. For more information see - Documentation/mm/slub.rst. + Documentation/admin-guide/mm/slab.rst. (slub_debug legacy name also accepted for now) + Using this option implies the "no_hash_pointers" + option which can be undone by adding the + "hash_pointers=always" option. + slab_max_order= [MM] Determines the maximum allowed order for slabs. A high setting may cause OOMs due to memory