| /linux/net/ethtool/ |
| H A D | mm.c | 165 * ETHTOOL_MSG_MM_GET replies. For example, a port with verification in mm_state_to_cfg()
219 NL_SET_ERR_MSG(extack, "Verification requires TX enabled"); in ethnl_set_mm()
309 * ethtool_mmsv_verify_timer - Timer for MAC Merge verification
365 /* If verification is disabled, configure FPE right away. in ethtool_mmsv_apply()
381 * ethtool_mmsv_stop() - Stop MAC Merge Software Verification
382 * @mmsv: MAC Merge Software Verification state
396 * ethtool_mmsv_link_state_handle() - Inform MAC Merge Software Verification
398 * @mmsv: MAC Merge Software Verification state
399 * @up: True if device carrier is up and able to pass verification packets
415 /* New link => maybe new partner => new verification process */ in ethtool_mmsv_link_state_handle()
[all …]
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 12 scalability, but of verification of the filesystem structure. Scalabilty of the
15 is this very scalability that causes the verification problem.
50 verification of metadata values, looking for values that are in range (and hence
51 not detected by automated verification checks) but are not correct. Finding and
76 self identifying and we can do much more expansive automated verification of the
84 contain, a large amount of the manual verification work can be skipped.
129 present that the run-time verification is not detecting.
156 The verification is completely stateless - it is done independently of the
166 For read verification, the caller needs to specify the expected type of metadata
168 object matches what was expected. If the verification process fails, then it
[all …]
|
| /linux/tools/verification/rv/ |
| H A D | README.txt | 1 RV: Runtime Verification
3 Runtime Verification (RV) is a lightweight (yet rigorous) method that
4 complements classical exhaustive verification techniques (such as model
37 Runtime Verification:
38 Documentation/trace/rv/runtime-verification.rst
|
| /linux/kernel/trace/rv/ |
| H A D | Kconfig | 27 bool "Runtime Verification"
30 Enable the kernel runtime verification infrastructure. RV is a
32 exhaustive verification techniques (such as model checking and
38 Documentation/trace/rv/runtime-verification.rst
71 bool "Runtime verification reactors"
75 Enables the online runtime verification reactors. A runtime
|
| H A D | rv.c | 5 * This is the online Runtime Verification (RV) interface.
8 * exhaustive verification techniques (such as model checking and
22 * Silva. Efficient formal verification for the Linux kernel. In:
29 * and verification of the real-time Linux kernel. PhD Thesis, 2020.
33 * A monitor is the central part of the runtime verification of a system.
38 * In Linux terms, the runtime verification monitors are encapsulated
51 * | (instrumentation) | | (verification) | | (specification) |
65 * to control the verification session.
70 * a verification session. For instance, when a given monitor is enabled,
73 * when disabling the verification session.
[all …]
|
| /linux/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 16 # "HW" is the --hw argument. In addition, non-Sometimes verification
19 # in that file will be used to judge the assembly-language verification.
109 echo ' !!! Verification error' $litmus
112 echo ' !!! Verification error' >> $LKMM_DESTDIR/$litmusout 2>&1
122 echo " !!! Unexpected non-$outcome verification" $litmus
125 echo " !!! Unexpected non-$outcome verification" >> $LKMM_DESTDIR/$litmusout 2>&1
149 echo " $flag non-$outcome verification" $litmus
152 echo " $flag non-$outcome verification" >> $LKMM_DESTDIR/$litmusout 2>&1
|
| H A D | checkalllitmus.sh | 6 # litmus test. If the verification result does not match that specified
8 # "^^^". It also outputs verification results to a file whose name is
61 echo " ^^^ VERIFICATION MISMATCHES" 1>&2
|
| /linux/tools/testing/selftests/drivers/net/hw/ |
| H A D | ethtool_mm.sh | 54 # to verification frame) should be taken into consideration while the
57 # the link partner's verification frames.
61 # Wait for verification to finish
66 check_err "$?" "Verification did not succeed"
77 log_test "Manual configuration with verification: $tx to $rx"
101 check_err "$?" "Verification is not disabled"
111 log_test "Manual configuration without verification: $tx to $rx"
134 # Wait for verification to time out
139 check_fail "$?" "Verification succeeded when it shouldn't have"
150 log_test "Manual configuration with failed verification: $tx to $rx"
|
| /linux/crypto/asymmetric_keys/ |
| H A D | Kconfig | 9 verification.
22 If signature generation and/or verification are to be used,
69 bool "Support for PE file signature verification"
80 tristate "Run FIPS selftests on the X.509+PKCS7 signature verification"
83 verification code, using some built in data. This is required
|
| /linux/Documentation/trace/rv/ |
| H A D | linear_temporal_logic.rst | 7 Runtime verification monitor is a verification technique which checks that the
78 verification, the `always` operator is usually desirable, to specify that
92 `tools/verification/rvgen`. The specification needs to be provided as a file,
131 Automatic Verification of Linear Temporal Logic. In: Dembiński, P., Średniawa,
132 M. (eds) Protocol Specification, Testing and Verification XV. PSTV 1995. IFIP
|
| H A D | index.rst | 2 Runtime Verification
9 runtime-verification.rst
|
| /linux/kernel/ |
| H A D | Kconfig.kexec | 60 verification for the corresponding kernel image type being
68 This option makes kernel signature verification mandatory for
72 bool "Enable Image signature verification support (ARM)"
78 Enable Image signature verification support.
81 bool "Enable bzImage signature verification support"
87 Enable bzImage signature verification support.
|
| /linux/Documentation/security/ |
| H A D | digsig.rst | 2 Digital Signature Verification API
19 Digital signature verification API provides a method to verify digital signature.
22 Digital signature verification is implemented using cut-down kernel port of
58 digsig_verify() - digital signature verification with public key
62 * digsig_verify() - digital signature verification with public key
|
| /linux/security/integrity/ |
| H A D | Kconfig | 10 Measurement Architecture (IMA), Extended Verification Module
11 (EVM), IMA-appraisal extension, digital signature verification
20 bool "Digital signature verification using multiple keyrings"
25 This option enables digital signature verification support
43 This option enables digital signature verification using
|
| /linux/Documentation/tools/rv/ |
| H A D | rv.rst | 7 Runtime Verification
20 Runtime Verification (**RV**) is a lightweight (yet rigorous) method argument
21 for formal verification with a practical approach for complex systems.
28 verification (rv) monitors.
|
| /linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 100 verification`_. This approach should be used only with great care.
147 if the `Built-in signature verification`_ feature is being used. It
250 This ioctl is useful for cases where the verity verification should be
255 compatible verification of the file. This only makes sense if the
292 signature verification`_.
306 implement fs-verity compatible verification anyway (though absent a
363 would circumvent the data verification.
370 opening the file will fail. See `Built-in signature verification`_.
452 Built-in signature verification
456 verification of fs-verity builtin signatures.
[all …]
|
| H A D | btrfs.rst | 24 * Scrub (on-line checksum verification)
33 * Read/write metadata verification
|
| /linux/net/sctp/ |
| H A D | sm_statefuns.c | 212 * Verification Tag: 8.5.1(C), sctpimpguide 2.41.
216 * if the Verification Tag field of the packet matches its own tag and
305 * Verification Tag field to Tag_A, and also provide its own
306 * Verification Tag (Tag_Z) in the Initiate Tag field.
308 * Verification Tag: Must be 0.
359 /* 3.1 A packet containing an INIT chunk MUST have a zero Verification in sctp_sf_do_5_1B_init()
505 * Verification Tag: 3.3.3
684 * Verification Tag: 8.5.1 Exceptions in Verification Tag Rules
729 * chunk header. More detailed verification is done in sctp_sf_do_5_1D_ce()
913 * Verification Tag:
[all …]
|
| /linux/fs/verity/ |
| H A D | Kconfig | 21 hash), or (b) authenticity verification (comparing the hash
36 This option adds support for in-kernel verification of
41 alternatives (such as userspace signature verification, and
|
| H A D | signature.c | 3 * Verification of builtin signatures
9 * This file implements verification of fs-verity builtin signatures. Please
12 * verification, and IMA appraisal) can be much better. For details about the
22 #include <linux/verification.h>
|
| /linux/Documentation/crypto/ |
| H A D | asymmetric-keys.rst | 12 - Signature verification.
112 1) Signature verification.
115 required for verification, but not currently supported, and others
119 Signature Verification
122 An operation is provided to perform cryptographic signature verification, using
225 Optional. This is the entry point for signature verification. The
346 for signature verification.
357 verification.
372 This allows for verification of certificate chains by adding each
|
| /linux/tools/testing/selftests/kvm/riscv/ |
| H A D | sbi_pmu_test.c | 292 "Event update verification failed: post [%lx] pre [%lx]\n", in test_pmu_event()
308 "Counter reinitialization verification failed : post [%lx] pre [%lx]\n", in test_pmu_event()
318 "Event update verification failed: post [%lx] pre [%lx]\n", in test_pmu_event()
342 "Event update verification failed: post [%lx] pre [%lx]\n", in test_pmu_event_snapshot()
360 "Counter reinitialization verification failed : post [%lx] pre [%lx]\n", in test_pmu_event_snapshot()
371 "Event update verification failed: post [%lx] pre [%lx]\n", in test_pmu_event_snapshot()
717 pr_info("SBI PMU event verification test : PASS\n"); in main()
722 pr_info("SBI PMU event verification with snapshot test : PASS\n"); in main()
727 pr_info("SBI PMU event verification with overflow test : PASS\n"); in main()
|
| /linux/drivers/s390/cio/ |
| H A D | device_fsm.c | 397 * timeout (or if sense pgid during path verification detects the device in ccw_device_recognition()
497 /* Repeat path verification? */ in ccw_device_verify_done()
565 /* Start initial path verification. */ in ccw_device_online()
643 * Handle path verification event in offline state.
654 * Handle path verification event.
681 * to the device driver. Can't do path verification now, in ccw_device_online_verify()
687 /* Device is idle, we can do the path verification. */ in ccw_device_online_verify()
693 * Handle path verification event in boxed state.
788 /* Start delayed path verification. */ in ccw_device_irq()
866 /* Start delayed path verification. */ in ccw_device_w4sense()
[all …]
|
| /linux/drivers/net/ethernet/mscc/ |
| H A D | ocelot_mm.c | 120 "Port %d MAC Merge verification state %s\n", in ocelot_mm_update_port_status()
137 …"Unexpected P-frame received on port %d while verification was unsuccessful or not yet verified\n", in ocelot_mm_update_port_status()
145 …"Unexpected P-frame requested to be transmitted on port %d while verification was unsuccessful or … in ocelot_mm_update_port_status()
293 * verification state machine in ocelot_mm_init()
|
| /linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | sharedbuffer_configuration.py | 215 log_test("pool {} of sb {} set verification".format(pool["pool"],
260 log_test("tc bind existence for port {} verification".format(port.name), err_msg)
285 log_test("tc bind {}-{} of sb {} set verification".format(tcbind["dlportname"],
332 log_test("port pool existence for port {} verification".format(port.name), err_msg)
352 log_test("port pool {}-{} of sb {} set verification".format(portpool["dlportname"],
|