Kconfig.debug 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. menu "Kernel hacking"
  2. config TRACE_IRQFLAGS_SUPPORT
  3. def_bool y
  4. source "lib/Kconfig.debug"
  5. config STRICT_DEVMEM
  6. def_bool y
  7. prompt "Filter access to /dev/mem"
  8. ---help---
  9. This option restricts access to /dev/mem. If this option is
  10. disabled, you allow userspace access to all memory, including
  11. kernel and userspace memory. Accidental memory access is likely
  12. to be disastrous.
  13. Memory access is required for experts who want to debug the kernel.
  14. If you are unsure, say Y.
  15. config DEBUG_STRICT_USER_COPY_CHECKS
  16. def_bool n
  17. prompt "Strict user copy size checks"
  18. ---help---
  19. Enabling this option turns a certain set of sanity checks for user
  20. copy operations into compile time warnings.
  21. The copy_from_user() etc checks are there to help test if there
  22. are sufficient security checks on the length argument of
  23. the copy operation, by having gcc prove that the argument is
  24. within bounds.
  25. If unsure, or if you run an older (pre 4.4) gcc, say N.
  26. config S390_PTDUMP
  27. bool "Export kernel pagetable layout to userspace via debugfs"
  28. depends on DEBUG_KERNEL
  29. select DEBUG_FS
  30. ---help---
  31. Say Y here if you want to show the kernel pagetable layout in a
  32. debugfs file. This information is only useful for kernel developers
  33. who are working in architecture specific areas of the kernel.
  34. It is probably not a good idea to enable this feature in a production
  35. kernel.
  36. If in doubt, say "N"
  37. config DEBUG_SET_MODULE_RONX
  38. def_bool y
  39. depends on MODULES
  40. endmenu