| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 136 Hash blocks are still verified each time they are read from the hash device,
138 blocks, and a hash block will not be verified any more after all the data
139 blocks it covers have been verified anyway.
167 dm-verity is meant to be set up as part of a verified boot path. This
173 After instantiation, all hashes will be verified on-demand during
174 disk access. If they cannot be verified up to the root node of the
184 corrupted data will be verified using the cryptographic hash of the
226 the command-line is verified.
|
| /linux/crypto/asymmetric_keys/ |
| H A D | pkcs7_trust.c | 40 if (x509->verified) in pkcs7_validate_trust_one()
41 goto verified; in pkcs7_validate_trust_one()
124 verified: in pkcs7_validate_trust_one()
126 x509->verified = true; in pkcs7_validate_trust_one()
128 p->verified = true; in pkcs7_validate_trust_one()
|
| /linux/fs/verity/ |
| H A D | verify.c | 42 * @hpage, has already been verified.
53 * to directly indicate whether the page's block has been verified. in is_hash_block_verified()
64 * to indicate whether each hash block has been verified. in is_hash_block_verified()
67 * re-instantiated from the backing storage are re-verified. To do in is_hash_block_verified()
81 * bitmap bit again at worst causes a hash block to be verified in is_hash_block_verified()
111 * only ascend the tree until an already-verified hash block is seen, and then
170 * the way until we find a hash block that has already been verified, or in verify_data_block()
239 * Mark the hash block as verified. This must be atomic and in verify_data_block()
240 * idempotent, as the same hash block might be verified by in verify_data_block()
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | chromeos-acpi-device.rst | 40 - Chrome OS verified boot data
284 - Offset in CMOS bank 0 of the verified boot non-volatile storage block, counting from
290 - Size in bytes of the verified boot non-volatile storage block.
306 VDTA (Chrome OS verified boot data)
308 This control method returns the verified boot data block shared between the firmware
317 A buffer containing the verified boot data block.
|
| /linux/security/integrity/ima/ |
| H A D | Kconfig | 198 be signed and verified by a public key on the trusted IMA
201 Kernel image signatures can not be verified by the original
211 and verified by a public key on the trusted IMA keyring.
213 Kernel module signatures can only be verified by IMA-appraisal,
223 and verified by a key on the trusted IMA keyring.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | test_stack_var_off.c | 40 * read would be rejected because the stack slot cannot be verified as in probe()
42 * stack slot still cannot be verified, but the write inhibits the in probe()
|
| /linux/Documentation/gpu/nova/core/ |
| H A D | falcon.rst | 34 the chip. The HS binary includes a signature in it which is verified at boot.
62 memory into the Falcon's IMEM/DMEM. Once the HS ucode is loaded, it is verified
65 Once the verified HS code is running on a Falcon, it can verify and load other
80 verified by the hardware and run, the CPU itself typically does not load
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-chromeos-acpi | 132 Returns offset in CMOS bank 0 of the verified boot non-volatile
142 Return the size in bytes of the verified boot non-volatile
150 Returns the verified boot data block shared between the
|
| H A D | sysfs-class-chromeos-driver-cros-ec-vbc | 5 Read/write the verified boot context data included on a
|
| /linux/drivers/md/dm-vdo/ |
| H A D | dedupe.c | 243 /* True if the advice has been verified to be a true duplicate */
244 bool verified; member
253 * If verified is false, this is the location of a possible duplicate. If verified is true,
254 * it is the verified location of a true duplicate.
639 if (!lock->verified) { in finish_unlocking()
651 * With the lock released, the verified duplicate block may already have changed and will in finish_unlocking()
652 * need to be re-verified if a waiter arrived. in finish_unlocking()
654 lock->verified = false; in finish_unlocking()
760 * Send it on the verified dedupe path. The agent is done with the lock, but the in finish_updating()
795 VDO_ASSERT_LOG_ONLY(lock->verified, "new advice should have been verified"); in start_updating()
[all …]
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | user.rst | 26 verified to be below the per user limit in that user namespace.
30 in (user namespaces can be nested) and verified to be below the per user
|
| /linux/drivers/md/ |
| H A D | dm-verity-verify-sig.c | 109 * @root_hash: For verity, the roothash/data to be verified.
110 * @root_hash_len: Size of the roothash/data to be verified.
|
| /linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 26 automatically verified against the file's Merkle tree. Reads of any
95 files with a verified fs-verity's built-in signature. For
479 that contain a verified built-in fsverity signature.
515 files with a verified fs-verity builtin signature to perform certain
600 fs-verity. In this case, the plaintext data is verified rather than
651 fs-verity ensures that all reads of a verity file's data are verified,
655 already verified). Below, we describe how filesystems implement this.
682 blocks until an already-verified hash block is seen. It then verifies
702 encrypted, the data must be decrypted before being verified. To
885 Uptodate until they've been verified. Currently, each
|
| /linux/drivers/gpu/drm/amd/display/dc/link/ |
| H A D | link_resource.c | 94 /* remove 128b/132b encoding capability by limiting verified link rate to HBR3 */ in link_restore_res_map()
108 /* remove 128b/132b encoding capability by limiting verified link rate to HBR3 */ in link_restore_res_map()
|
| /linux/drivers/comedi/drivers/ |
| H A D | ni_mio_cs.c | 58 .caldac = { mb88341 }, /* verified */
72 .caldac = { ad8804_debug }, /* verified */
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 117 then be verified by certification in user-space. Therefore, this chain
170 certificate itself must be verified to chain back to the manufacturer
206 signature of the returned certifyInfo is verified against the public
|
| /linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | qos_dscp_bridge.sh | 7 # tag is verified at $h2.
11 # verified at $h1--it should match the original tag.
|
| /linux/drivers/net/ethernet/mscc/ |
| H A D | ocelot_mm.c | 137 …"Unexpected P-frame received on port %d while verification was unsuccessful or not yet verified\n", in ocelot_mm_update_port_status()
145 …e transmitted on port %d while verification was unsuccessful or not yet verified, or MM_TX_ENA=0\n… in ocelot_mm_update_port_status()
|
| /linux/Documentation/arch/x86/ |
| H A D | shstk.rst | 44 An application's CET capability is marked in its ELF note and can be verified
138 verified and restored by the kernel. The kernel will also push the normal
|
| /linux/tools/memory-model/scripts/ |
| H A D | checktheselitmus.sh | 41 echo All litmus tests verified as was expected. 1>&2
|
| /linux/include/uapi/linux/ |
| H A D | tdx-guest.h | 25 * service, so the generated TDREPORT can be uniquely verified.
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | arm,corstone1000.yaml | 14 ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | LoadPin.rst | 8 such as dm-verity or CDROM. This allows systems that have a verified
|
| /linux/fs/nilfs2/ |
| H A D | page.h | 29 BUFFER_FNS(NILFS_Checked, nilfs_checked) /* buffer is verified */
|
| /linux/tools/testing/selftests/net/tcp_ao/ |
| H A D | seq-ext.c | 167 synchronize_threads(); /* 6: verified => closed */ in server_fn()
244 synchronize_threads(); /* 6: verified => closed */ in client_fn()
|