Loading Documentation/ABI/testing/sysfs-kernel-oops_count 0 → 100644 +6 −0 Original line number Diff line number Diff line What: /sys/kernel/oops_count Date: November 2022 KernelVersion: 6.2.0 Contact: Linux Kernel Hardening List <linux-hardening@vger.kernel.org> Description: Shows how many times the system has Oopsed since last boot. Documentation/ABI/testing/sysfs-kernel-warn_count 0 → 100644 +6 −0 Original line number Diff line number Diff line What: /sys/kernel/warn_count Date: November 2022 KernelVersion: 6.2.0 Contact: Linux Kernel Hardening List <linux-hardening@vger.kernel.org> Description: Shows how many times the system has Warned since last boot. Documentation/admin-guide/sysctl/kernel.rst +19 −0 Original line number Diff line number Diff line Loading @@ -557,6 +557,15 @@ numa_balancing_scan_size_mb is how many megabytes worth of pages are scanned for a given scan. oops_limit ========== Number of kernel oopses after which the kernel should panic when ``panic_on_oops`` is not set. Setting this to 0 disables checking the count. Setting this to 1 has the same effect as setting ``panic_on_oops=1``. The default value is 10000. osrelease, ostype & version: ============================ Loading Loading @@ -1177,6 +1186,16 @@ entry will default to 2 instead of 0. 2 Unprivileged calls to ``bpf()`` are disabled = ============================================================= warn_limit ========== Number of kernel warnings after which the kernel should panic when ``panic_on_warn`` is not set. Setting this to 0 disables checking the warning count. Setting this to 1 has the same effect as setting ``panic_on_warn=1``. The default value is 0. watchdog: ========= Loading Documentation/driver-api/spi.rst +2 −2 Original line number Diff line number Diff line Loading @@ -25,8 +25,8 @@ hardware, which may be as simple as a set of GPIO pins or as complex as a pair of FIFOs connected to dual DMA engines on the other side of the SPI shift register (maximizing throughput). Such drivers bridge between whatever bus they sit on (often the platform bus) and SPI, and expose the SPI side of their device as a :c:type:`struct spi_master <spi_master>`. SPI devices are children of that master, the SPI side of their device as a :c:type:`struct spi_controller <spi_controller>`. SPI devices are children of that master, represented as a :c:type:`struct spi_device <spi_device>` and manufactured from :c:type:`struct spi_board_info <spi_board_info>` descriptors which are usually provided by Loading Documentation/fault-injection/fault-injection.rst +9 −7 Original line number Diff line number Diff line Loading @@ -74,8 +74,8 @@ configuration of fault-injection capabilities. - /sys/kernel/debug/fail*/times: specifies how many times failures may happen at most. A value of -1 means "no limit". specifies how many times failures may happen at most. A value of -1 means "no limit". - /sys/kernel/debug/fail*/space: Loading Loading @@ -163,11 +163,13 @@ configuration of fault-injection capabilities. - ERRNO: retval must be -1 to -MAX_ERRNO (-4096). - ERR_NULL: retval must be 0 or -1 to -MAX_ERRNO (-4096). - /sys/kernel/debug/fail_function/<functiuon-name>/retval: - /sys/kernel/debug/fail_function/<function-name>/retval: specifies the "error" return value to inject to the given function for given function. This will be created when user specifies new injection entry. specifies the "error" return value to inject to the given function. This will be created when the user specifies a new injection entry. Note that this file only accepts unsigned values. So, if you want to use a negative errno, you better use 'printf' instead of 'echo', e.g.: $ printf %#x -12 > retval Boot option ^^^^^^^^^^^ Loading Loading @@ -331,7 +333,7 @@ Application Examples FAILTYPE=fail_function FAILFUNC=open_ctree echo $FAILFUNC > /sys/kernel/debug/$FAILTYPE/inject echo -12 > /sys/kernel/debug/$FAILTYPE/$FAILFUNC/retval printf %#x -12 > /sys/kernel/debug/$FAILTYPE/$FAILFUNC/retval echo N > /sys/kernel/debug/$FAILTYPE/task-filter echo 100 > /sys/kernel/debug/$FAILTYPE/probability echo 0 > /sys/kernel/debug/$FAILTYPE/interval Loading Loading
Documentation/ABI/testing/sysfs-kernel-oops_count 0 → 100644 +6 −0 Original line number Diff line number Diff line What: /sys/kernel/oops_count Date: November 2022 KernelVersion: 6.2.0 Contact: Linux Kernel Hardening List <linux-hardening@vger.kernel.org> Description: Shows how many times the system has Oopsed since last boot.
Documentation/ABI/testing/sysfs-kernel-warn_count 0 → 100644 +6 −0 Original line number Diff line number Diff line What: /sys/kernel/warn_count Date: November 2022 KernelVersion: 6.2.0 Contact: Linux Kernel Hardening List <linux-hardening@vger.kernel.org> Description: Shows how many times the system has Warned since last boot.
Documentation/admin-guide/sysctl/kernel.rst +19 −0 Original line number Diff line number Diff line Loading @@ -557,6 +557,15 @@ numa_balancing_scan_size_mb is how many megabytes worth of pages are scanned for a given scan. oops_limit ========== Number of kernel oopses after which the kernel should panic when ``panic_on_oops`` is not set. Setting this to 0 disables checking the count. Setting this to 1 has the same effect as setting ``panic_on_oops=1``. The default value is 10000. osrelease, ostype & version: ============================ Loading Loading @@ -1177,6 +1186,16 @@ entry will default to 2 instead of 0. 2 Unprivileged calls to ``bpf()`` are disabled = ============================================================= warn_limit ========== Number of kernel warnings after which the kernel should panic when ``panic_on_warn`` is not set. Setting this to 0 disables checking the warning count. Setting this to 1 has the same effect as setting ``panic_on_warn=1``. The default value is 0. watchdog: ========= Loading
Documentation/driver-api/spi.rst +2 −2 Original line number Diff line number Diff line Loading @@ -25,8 +25,8 @@ hardware, which may be as simple as a set of GPIO pins or as complex as a pair of FIFOs connected to dual DMA engines on the other side of the SPI shift register (maximizing throughput). Such drivers bridge between whatever bus they sit on (often the platform bus) and SPI, and expose the SPI side of their device as a :c:type:`struct spi_master <spi_master>`. SPI devices are children of that master, the SPI side of their device as a :c:type:`struct spi_controller <spi_controller>`. SPI devices are children of that master, represented as a :c:type:`struct spi_device <spi_device>` and manufactured from :c:type:`struct spi_board_info <spi_board_info>` descriptors which are usually provided by Loading
Documentation/fault-injection/fault-injection.rst +9 −7 Original line number Diff line number Diff line Loading @@ -74,8 +74,8 @@ configuration of fault-injection capabilities. - /sys/kernel/debug/fail*/times: specifies how many times failures may happen at most. A value of -1 means "no limit". specifies how many times failures may happen at most. A value of -1 means "no limit". - /sys/kernel/debug/fail*/space: Loading Loading @@ -163,11 +163,13 @@ configuration of fault-injection capabilities. - ERRNO: retval must be -1 to -MAX_ERRNO (-4096). - ERR_NULL: retval must be 0 or -1 to -MAX_ERRNO (-4096). - /sys/kernel/debug/fail_function/<functiuon-name>/retval: - /sys/kernel/debug/fail_function/<function-name>/retval: specifies the "error" return value to inject to the given function for given function. This will be created when user specifies new injection entry. specifies the "error" return value to inject to the given function. This will be created when the user specifies a new injection entry. Note that this file only accepts unsigned values. So, if you want to use a negative errno, you better use 'printf' instead of 'echo', e.g.: $ printf %#x -12 > retval Boot option ^^^^^^^^^^^ Loading Loading @@ -331,7 +333,7 @@ Application Examples FAILTYPE=fail_function FAILFUNC=open_ctree echo $FAILFUNC > /sys/kernel/debug/$FAILTYPE/inject echo -12 > /sys/kernel/debug/$FAILTYPE/$FAILFUNC/retval printf %#x -12 > /sys/kernel/debug/$FAILTYPE/$FAILFUNC/retval echo N > /sys/kernel/debug/$FAILTYPE/task-filter echo 100 > /sys/kernel/debug/$FAILTYPE/probability echo 0 > /sys/kernel/debug/$FAILTYPE/interval Loading
