Home
last modified time | relevance | path

Searched full:verified (Results 1 – 25 of 454) sorted by relevance

12345678910>>...19

/linux-6.12.1/Documentation/admin-guide/device-mapper/
Dverity.rst127 Hash blocks are still verified each time they are read from the hash device,
129 blocks, and a hash block will not be verified any more after all the data
130 blocks it covers have been verified anyway.
151 dm-verity is meant to be set up as part of a verified boot path. This
157 After instantiation, all hashes will be verified on-demand during
158 disk access. If they cannot be verified up to the root node of the
168 corrupted data will be verified using the cryptographic hash of the
210 the command-line is verified.
/linux-6.12.1/fs/verity/
Dverify.c17 * @hpage, has already been verified.
28 * to directly indicate whether the page's block has been verified. in is_hash_block_verified()
39 * to indicate whether each hash block has been verified. in is_hash_block_verified()
42 * re-instantiated from the backing storage are re-verified. To do in is_hash_block_verified()
56 * bitmap bit again at worst causes a hash block to be verified in is_hash_block_verified()
86 * only ascend the tree until an already-verified hash block is seen, and then
140 * the way until we find a hash block that has already been verified, or in verify_data_block()
210 * Mark the hash block as verified. This must be atomic and in verify_data_block()
211 * idempotent, as the same hash block might be verified by in verify_data_block()
/linux-6.12.1/crypto/asymmetric_keys/
Dpkcs7_trust.c40 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()
Dpkcs7_verify.c358 pr_devel("Verified signature %u\n", sinfo->index); in pkcs7_verify_one()
366 * @pkcs7: The PKCS#7 message to be verified
372 * message can be verified.
467 * @data: The data to be verified
/linux-6.12.1/security/integrity/ima/
DKconfig198 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-6.12.1/Documentation/firmware-guide/acpi/
Dchromeos-acpi-device.rst40 - 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-6.12.1/tools/testing/selftests/bpf/progs/
Dtest_stack_var_off.c40 * 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-6.12.1/drivers/mtd/tests/
Dsubpagetest.c258 pr_info("verified up to eraseblock %u\n", i); in verify_all_eraseblocks_ff()
264 pr_info("verified %u eraseblocks\n", i); in verify_all_eraseblocks_ff()
355 pr_info("verified up to eraseblock %u\n", i); in mtd_subpagetest_init()
361 pr_info("verified %u eraseblocks\n", i); in mtd_subpagetest_init()
399 pr_info("verified up to eraseblock %u\n", i); in mtd_subpagetest_init()
405 pr_info("verified %u eraseblocks\n", i); in mtd_subpagetest_init()
Doobtest.c326 pr_info("verified up to eraseblock %u\n", i); in verify_all_eraseblocks()
332 pr_info("verified %u eraseblocks\n", i); in verify_all_eraseblocks()
440 pr_info("verified up to eraseblock %u\n", i); in mtd_oobtest_init()
446 pr_info("verified %u eraseblocks\n", i); in mtd_oobtest_init()
704 pr_info("verified up to eraseblock %u\n", i); in mtd_oobtest_init()
710 pr_info("verified %u eraseblocks\n", i); in mtd_oobtest_init()
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-driver-chromeos-acpi132 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
Dsysfs-class-chromeos-driver-cros-ec-vbc5 Read/write the verified boot context data included on a
/linux-6.12.1/Documentation/admin-guide/sysctl/
Duser.rst26 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-6.12.1/drivers/md/dm-vdo/
Ddedupe.c243 /* 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-6.12.1/drivers/md/
Ddm-verity-verify-sig.c100 * @root_hash: For verity, the roothash/data to be verified.
101 * @root_hash_len: Size of the roothash/data to be verified.
/linux-6.12.1/drivers/clk/sunxi-ng/
Dccu-sun50i-h6-r.c81 * of the hardware block is verified with "3.1 Memory Mapping" chapter in
82 * "Allwinner H6 V200 User Manual V1.1"; and the parent APB buses are verified
117 * this mod clock is proven by BSP clock header, and the dividers are verified
/linux-6.12.1/drivers/gpu/drm/amd/display/dc/link/
Dlink_resource.c94 /* 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-6.12.1/Documentation/filesystems/
Dfsverity.rst26 automatically verified against the file's Merkle tree. Reads of any
95 files with a verified fs-verity's built-in signature. For
474 that contain a verified built-in fsverity signature.
510 files with a verified fs-verity builtin signature to perform certain
595 fs-verity. In this case, the plaintext data is verified rather than
646 fs-verity ensures that all reads of a verity file's data are verified,
650 already verified). Below, we describe how filesystems implement this.
677 blocks until an already-verified hash block is seen. It then verifies
697 encrypted, the data must be decrypted before being verified. To
880 Uptodate until they've been verified. Currently, each
/linux-6.12.1/drivers/gpu/drm/nouveau/include/nvrm/535.113.01/nvidia/arch/nvalloc/common/inc/gsp/
Dgsp_fw_wpr_meta.h164 NvU64 verified; // 0x0 -> unverified, 0xa0a0a0a0a0a0a0a0 -> verified member
/linux-6.12.1/drivers/comedi/drivers/
Dni_mio_cs.c58 .caldac = { mb88341 }, /* verified */
72 .caldac = { ad8804_debug }, /* verified */
/linux-6.12.1/Documentation/security/tpm/
Dtpm-security.rst117 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-6.12.1/tools/testing/selftests/drivers/net/mlxsw/
Dqos_dscp_bridge.sh7 # tag is verified at $h2.
11 # verified at $h1--it should match the original tag.
/linux-6.12.1/tools/memory-model/scripts/
Dchecktheselitmus.sh41 echo All litmus tests verified as was expected. 1>&2
/linux-6.12.1/include/uapi/linux/
Dtdx-guest.h25 * service, so the generated TDREPORT can be uniquely verified.
/linux-6.12.1/Documentation/devicetree/bindings/arm/
Darm,corstone1000.yaml14 ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that
/linux-6.12.1/Documentation/arch/x86/
Dshstk.rst44 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

12345678910>>...19