| /linux/lib/kunit/ |
| H A D | try-catch-impl.h | 20 kunit_try_catch_func_t catch, in kunit_try_catch_init() argument
25 try_catch->catch = catch; in kunit_try_catch_init()
|
| H A D | try-catch.c | 50 try_catch->catch(try_catch->context); in kunit_try_catch_run()
89 try_catch->catch(try_catch->context); in kunit_try_catch_run()
|
| /linux/tools/testing/kunit/test_data/ |
| H A D | test_kernel_panic_interrupt.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_config_printk_time.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_pound_sign.log | 15 [ 0.060000] # Subtest: kunit-try-catch-test
19 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_output_with_prefix_isolated_correctly.log | 14 [ 0.060000] # Subtest: kunit-try-catch-test
18 [ 0.060000] ok 2 - kunit-try-catch-test
|
| H A D | test_pound_no_prefix.log | 15 # Subtest: kunit-try-catch-test
19 ok 2 - kunit-try-catch-test
|
| H A D | test_multiple_prefixes.log | 13 [ 0.060000][ T1] # Subtest: kunit-try-catch-test
17 [ 0.060000][ T1] ok 2 - kunit-try-catch-test
|
| H A D | test_interrupted_tap_output.log | 19 [ 0.060000] # Subtest: kunit-try-catch-test
23 [ 0.060000] ok 2 - kunit-try-catch-test
|
| /linux/include/kunit/ |
| H A D | try-catch.h | 49 kunit_try_catch_func_t catch; member
|
| /linux/arch/parisc/ |
| H A D | Kconfig.debug | 9 to catch memory overwrites at runtime. For more advanced
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | verify_sig_setup.sh | 89 catch()
127 trap 'catch "$?" "${LOG_FILE}"' EXIT
84 catch() global() function
|
| H A D | vmtest.sh | 359 catch() function
|
| /linux/tools/sched_ext/ |
| H A D | Kconfig | 43 # Additional debugging information (useful to catch potential locking issues)
|
| /linux/arch/xtensa/ |
| H A D | Kconfig.debug | 31 It is easy to make wrong hardware configuration, this test should catch it early.
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 79 * but GPIO3_C6 would catch this HW soldering issue.
101 * but GPIO3_C6 would catch this HW soldering issue.
|
| /linux/Documentation/dev-tools/ |
| H A D | ubsan.rst | 8 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
|
| /linux/drivers/platform/x86/intel/pmt/ |
| H A D | Kconfig | 64 helping developers catch regressions and ensure code quality during changes.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | architecture.rst | 103 `lib/kunit/try-catch.c <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/lib…
|
| /linux/Documentation/trace/ |
| H A D | stm.rst | 70 catch-all entry "default" will be used, if it exists. This entry also
115 node, the stm core will use the catch-all entry "default", if one
|
| /linux/Documentation/arch/powerpc/ |
| H A D | kasan.txt | 23 - It would be good to support inline instrumentation so as to be able to catch
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 99 called scmi_power_control. Note this may needed early in boot to catch
|
| /linux/Documentation/PCI/ |
| H A D | acpi-info.rst | 66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 159 As such, we cannot catch all types of corruption that can occur within a block
169 marks the object being read as EFSCORRUPTED. The caller needs to catch this
187 error for the higher layers to catch.
|
| /linux/Documentation/driver-api/mtd/ |
| H A D | spi-nor.rst | 184 we won't catch it, thus test the erase again::
|