Changes in Kconfig.debug

626db6ee - sparc: select FRAME_POINTER instead of redefining it

Thu, 15 Feb 2024 13:57:49 +0000

sparc: select FRAME_POINTER instead of redefining itBecause FRAME_POINTER is defined in lib/Kconfig.debug, the arch Kconfigshould select it.Add 'select FRAME_POINTER' to MCOUNT. ARCH_WANT_FRAME_POINTERS mustalso be selected to avoid the unmet dependency warning.Signed-off-by: Masahiro Yamada Reviewed-by: Randy Dunlap Signed-off-by: Andreas Larsson Link: https://lore.kernel.org/r/20240215135749.1909812-1-masahiroy@kernel.org List of files: /linux-6.15/arch/sparc/Kconfig.debug

47f4cb43 - watchdog/sparc64: define HARDLOCKUP_DETECTOR_SPARC64

Fri, 16 Jun 2023 15:06:17 +0000

watchdog/sparc64: define HARDLOCKUP_DETECTOR_SPARC64The HAVE_ prefix means that the code could be enabled. Add anothervariable for HAVE_HARDLOCKUP_DETECTOR_SPARC64 without this prefix.It will be set when it should be built. It will make it compatiblewith the other hardlockup detectors.Before, it is far from obvious that the SPARC64 variant is actually used:$> make ARCH=sparc64 defconfig$> grep HARDLOCKUP_DETECTOR .configCONFIG_HAVE_HARDLOCKUP_DETECTOR_BUDDY=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_SPARC64=yAfter, it is more clear:$> make ARCH=sparc64 defconfig$> grep HARDLOCKUP_DETECTOR .configCONFIG_HAVE_HARDLOCKUP_DETECTOR_BUDDY=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_SPARC64=yCONFIG_HARDLOCKUP_DETECTOR_SPARC64=yLink: https://lkml.kernel.org/r/20230616150618.6073-6-pmladek@suse.comSigned-off-by: Petr Mladek Reviewed-by: Douglas Anderson Cc: Christophe Leroy Cc: "David S. Miller" Cc: Michael Ellerman Cc: Nicholas Piggin Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/sparc/Kconfig.debug

a5fcc236 - watchdog/hardlockup: make HAVE_NMI_WATCHDOG sparc64-specific

Fri, 16 Jun 2023 15:06:16 +0000

watchdog/hardlockup: make HAVE_NMI_WATCHDOG sparc64-specificThere are several hardlockup detector implementations and several Kconfigvalues which allow selection and build of the preferred one.CONFIG_HARDLOCKUP_DETECTOR was introduced by the commit 23637d477c1f53acb("lockup_detector: Introduce CONFIG_HARDLOCKUP_DETECTOR") in v2.6.36.It was a preparation step for introducing the new generic perf hardlockupdetector.The existing arch-specific variants did not support the to-be-createdgeneric build configurations, sysctl interface, etc. This distinctionwas made explicit by the commit 4a7863cc2eb5f98 ("x86, nmi_watchdog:Remove ARCH_HAS_NMI_WATCHDOG and rely on CONFIG_HARDLOCKUP_DETECTOR")in v2.6.38.CONFIG_HAVE_NMI_WATCHDOG was introduced by the commit d314d74c695f967e105("nmi watchdog: do not use cpp symbol in Kconfig") in v3.4-rc1. It replacedthe above mentioned ARCH_HAS_NMI_WATCHDOG. At that time, it was still usedby three architectures, namely blackfin, mn10300, and sparc.The support for blackfin and mn10300 architectures has been completelydropped some time ago. And sparc is the only architecture with the historicNMI watchdog at the moment.And the old sparc implementation is really special. It is always built onsparc64. It used to be always enabled until the commit 7a5c8b57cec93196b("sparc: implement watchdog_nmi_enable and watchdog_nmi_disable") addedin v4.10-rc1.There are only few locations where the sparc64 NMI watchdog interactswith the generic hardlockup detectors code: + implements arch_touch_nmi_watchdog() which is called from the generic touch_nmi_watchdog() + implements watchdog_hardlockup_enable()/disable() to support /proc/sys/kernel/nmi_watchdog + is always preferred over other generic watchdogs, see CONFIG_HARDLOCKUP_DETECTOR + includes asm/nmi.h into linux/nmi.h because some sparc-specific functions are needed in sparc-specific code which includes only linux/nmi.h.The situation became more complicated after the commit 05a4a95279311c3("kernel/watchdog: split up config options") and commit 2104180a53698df5("powerpc/64s: implement arch-specific hardlockup watchdog") in v4.13-rc1.They introduced HAVE_HARDLOCKUP_DETECTOR_ARCH. It was used for powerpcspecific hardlockup detector. It was compatible with the perf oneregarding the general boot, sysctl, and programming interfaces.HAVE_HARDLOCKUP_DETECTOR_ARCH was defined as a superset ofHAVE_NMI_WATCHDOG. It made some sense because all arch-specificdetectors had some common requirements, namely: + implemented arch_touch_nmi_watchdog() + included asm/nmi.h into linux/nmi.h + defined the default value for /proc/sys/kernel/nmi_watchdogBut it actually has made things pretty complicated when the genericbuddy hardlockup detector was added. Before the generic perf detectorwas newer supported together with an arch-specific one. But the buddydetector could work on any SMP system. It means that an architecturecould support both the arch-specific and buddy detector.As a result, there are few tricky dependencies. For example,CONFIG_HARDLOCKUP_DETECTOR depends on: ((HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_BUDDY) && !HAVE_NMI_WATCHDOG) || HAVE_HARDLOCKUP_DETECTOR_ARCHThe problem is that the very special sparc implementation is defined as: HAVE_NMI_WATCHDOG && !HAVE_HARDLOCKUP_DETECTOR_ARCHAnother problem is that the meaning of HAVE_NMI_WATCHDOG is far from clearwithout reading understanding the history.Make the logic less tricky and more self-explanatory by makingHAVE_NMI_WATCHDOG specific for the sparc64 implementation. And rename it toHAVE_HARDLOCKUP_DETECTOR_SPARC64.Note that HARDLOCKUP_DETECTOR_PREFER_BUDDY, HARDLOCKUP_DETECTOR_PERF,and HARDLOCKUP_DETECTOR_BUDDY may conflict only withHAVE_HARDLOCKUP_DETECTOR_ARCH. They depend on HARDLOCKUP_DETECTORand it is not longer enabled when HAVE_NMI_WATCHDOG is set.Link: https://lkml.kernel.org/r/20230616150618.6073-5-pmladek@suse.comSigned-off-by: Petr Mladek Reviewed-by: Douglas Anderson Cc: Christophe Leroy Cc: "David S. Miller" Cc: Michael Ellerman Cc: Nicholas Piggin Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/sparc/Kconfig.debug

4aae683f - tracing: Refactor TRACE_IRQFLAGS_SUPPORT in Kconfig

Sat, 31 Jul 2021 05:22:32 +0000

tracing: Refactor TRACE_IRQFLAGS_SUPPORT in KconfigMake architectures select TRACE_IRQFLAGS_SUPPORT instead ofhaving many defines.Link: https://lkml.kernel.org/r/20210731052233.4703-2-masahiroy@kernel.orgAcked-by: Heiko Carstens Acked-by: Vineet Gupta #arch/arcAcked-by: Michael Ellerman (powerpc)Acked-by: Catalin Marinas Acked-by: Max Filippov Signed-off-by: Masahiro Yamada Signed-off-by: Steven Rostedt (VMware) List of files: /linux-6.15/arch/sparc/Kconfig.debug

06ec64b8 - Kconfig: consolidate the "Kernel hacking" menu

Tue, 31 Jul 2018 11:39:31 +0000

Kconfig: consolidate the "Kernel hacking" menuMove the source of lib/Kconfig.debug and arch/$(ARCH)/Kconfig.debug tothe top-level Kconfig. For two architectures that means moving theirarch-specific symbols in that menu into a new arch Kconfig.debug file,and for a few more creating a dummy file so that we can include itunconditionally.Also move the actual 'Kernel hacking' menu to lib/Kconfig.debug, whereit belongs.Signed-off-by: Christoph Hellwig Signed-off-by: Masahiro Yamada List of files: /linux-6.15/arch/sparc/Kconfig.debug

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/sparc/Kconfig.debug

5ca43f6c - lib: consolidate DEBUG_STACK_USAGE option

Wed, 25 May 2011 00:13:36 +0000

lib: consolidate DEBUG_STACK_USAGE optionMost arches define CONFIG_DEBUG_STACK_USAGE exactly the same way. Move itto lib/Kconfig.debug so each arch doesn't have to define it. Thisobviously makes the option generic, but that's fine because the config isalready used in generic code.It's not obvious to me that sysrq-P actually does anything caution bykeeping the most inclusive wording.Signed-off-by: Stephen Boyd Cc: Chris Metcalf Acked-by: David S. Miller Acked-by: Richard Weinberger Acked-by: Mike Frysinger Cc: Russell King Cc: Hirokazu Takata Acked-by: Ralf Baechle Cc: Paul Mackerras Acked-by: Benjamin Herrenschmidt Cc: Chen Liqin Cc: Lennox Wu Cc: Ingo Molnar Cc: Thomas Gleixner Cc: "H. Peter Anvin" Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/sparc/Kconfig.debug

4cb6066a - sparc: Kill user copy check code.

Mon, 09 Aug 2010 07:45:46 +0000

sparc: Kill user copy check code.For whatever reason GCC isn't able to figure things out inthe control flow (in particular when min() and max() expressionsare involved) on sparc as well as it can on x86.So lots of useless incorrect user copy warnings get spewed and thefull-on compile failure mode of the user copy checks were never usableon sparc at all.People can debug these kinds of problems on x86.Signed-off-by: David S. Miller List of files: /linux-6.15/arch/sparc/Kconfig.debug

ddacd0bc - sparc64: Kill CONFIG_STACK_DEBUG code.

Tue, 13 Apr 2010 05:36:03 +0000

sparc64: Kill CONFIG_STACK_DEBUG code.The generic stack tracer does this job just as well.Signed-off-by: David S. Miller List of files: /linux-6.15/arch/sparc/Kconfig.debug

fb34035e - sparc: Use __builtin_object_size() to validate the buffer size for copy_from_user()

Fri, 11 Dec 2009 07:05:23 +0000

sparc: Use __builtin_object_size() to validate the buffer size for copy_from_user()This mirrors x86 commit 9f0cf4adb6aa0bfccf675c938124e68f7f06349d(x86: Use __builtin_object_size() to validate the buffer size for copy_from_user())Signed-off-by: David S. Miller List of files: /linux-6.15/arch/sparc/Kconfig.debug

ee3b4290 - generic debug pagealloc: build fix

Thu, 02 Apr 2009 23:56:30 +0000

generic debug pagealloc: build fixThis fixes a build failure with generic debug pagealloc: mm/debug-pagealloc.c: In function 'set_page_poison': mm/debug-pagealloc.c:8: error: 'struct page' has no member named 'debug_flags' mm/debug-pagealloc.c: In function 'clear_page_poison': mm/debug-pagealloc.c:13: error: 'struct page' has no member named 'debug_flags' mm/debug-pagealloc.c: In function 'page_poison': mm/debug-pagealloc.c:18: error: 'struct page' has no member named 'debug_flags' mm/debug-pagealloc.c: At top level: mm/debug-pagealloc.c:120: error: redefinition of 'kernel_map_pages' include/linux/mm.h:1278: error: previous definition of 'kernel_map_pages' was here mm/debug-pagealloc.c: In function 'kernel_map_pages': mm/debug-pagealloc.c:122: error: 'debug_pagealloc_enabled' undeclared (first use in this function)by fixing - debug_flags should be in struct page - define DEBUG_PAGEALLOC config option for all architecturesSigned-off-by: Akinobu Mita Reported-by: Alexander Beregalov Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/sparc/Kconfig.debug

6a11f75b - generic debug pagealloc

Tue, 31 Mar 2009 22:23:17 +0000

generic debug pageallocCONFIG_DEBUG_PAGEALLOC is now supported by x86, powerpc, sparc64, ands390. This patch implements it for the rest of the architectures byfilling the pages with poison byte patterns after free_pages() andverifying the poison patterns before alloc_pages().This generic one cannot detect invalid page accesses immediately butinvalid read access may cause invalid dereference by poisoned memory andinvalid write access can be detected after a long delay.Signed-off-by: Akinobu Mita Cc: Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/sparc/Kconfig.debug

5bb28a57 - sparc: unify Kconfig.debug

Sat, 15 Nov 2008 21:39:18 +0000

sparc: unify Kconfig.debugLet sparc and sparc64 use the same Kconfig.debugSigned-off-by: Sam Ravnborg Signed-off-by: David S. Miller List of files: /linux-6.15/arch/sparc/Kconfig.debug

e8dd1612 - [SPARC32]: Add irqflags.h to sparc32 and use it from generic code.

Thu, 27 Sep 2007 20:15:31 +0000

[SPARC32]: Add irqflags.h to sparc32 and use it from generic code.Added asm-sparc/irqflags.h and moved irq related code from system.h to it.Renamed local_irq functions to raw_local_irq in irq.c.Modified system.h to include linux/irqflags.h which includes asm/irqflags.h.Added TRACE_IRQFLAGS_SUPPORT to Kconfig.debug.This is the first step in adding IRQ-flags state tracing as outlined inDocumentation/irqflags-tracing.txt. These changes should be harmlessbecause they just move things around and rename them.The next step is making the lowlevel entry code modifications whichto be honest are beyond my capabilities at this point.Boot tested on an ss20 running an SMP kernel.Signed-off-by: Robert Reif Signed-off-by: David S. Miller List of files: /linux-6.15/arch/sparc/Kconfig.debug

1da177e4 - Linux-2.6.12-rc2

Sat, 16 Apr 2005 22:20:36 +0000

Linux-2.6.12-rc2Initial git repository build. I'm not bothering with the full history,even though we have it. We can create a separate "historical" gitarchive of that later if we want to, and in the meantime it's about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don't have a lot of goodinfrastructure for it.Let it rip! List of files: /linux-6.15/arch/sparc/Kconfig.debug