Home
last modified time | relevance | path

Searched refs:verity (Results 1 – 25 of 31) sorted by relevance

12

/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dfsverity.rst6 fs-verity: read-only file-based authenticity protection
12 fs-verity (``fs/verity/``) is a support layer that filesystems can
16 needed to support fs-verity.
18 fs-verity is similar to `dm-verity
19 <https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
21 filesystems supporting fs-verity, userspace can execute an ioctl that
30 the "fs-verity file digest", which is a hash that includes the Merkle
31 tree root hash) that fs-verity is enforcing for the file. This ioctl
34 fs-verity is essentially a way to hash a file in constant time,
41 By itself, the base fs-verity feature only provides integrity
[all …]
H A Dincfs.rst24 fs-verity support
H A Dubifs-authentication.rst32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
444 [DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst
/OK3568_Linux_fs/kernel/fs/verity/
H A DKconfig14 This option enables fs-verity. fs-verity is the dm-verity
17 ioctl to enable verity for a file, which causes the filesystem
29 fs-verity is especially useful on large files where not all
30 the contents may actually be needed. Also, fs-verity verifies
40 Enable debugging messages related to fs-verity by default.
42 Say N unless you are an fs-verity developer.
49 Support verifying signatures of verity files against the X.509
50 certificates that have been loaded into the ".fs-verity"
54 used to provide an authenticity guarantee for verity files, as
56 need to check that the verity bit is set in order to get an
/OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/
H A Dverity.rst6 ext4 supports fs-verity, which is a filesystem feature that provides
8 fs-verity is common to all filesystems that support it; see
10 fs-verity documentation. However, the on-disk layout of the verity
11 metadata is filesystem-specific. On ext4, the verity metadata is
25 - The verity descriptor, as documented in
32 - The size of the verity descriptor in bytes, as a 4-byte little
37 They can have EXT4_ENCRYPT_FL set, in which case the verity metadata
40 Verity files cannot have blocks allocated past the end of the verity
H A Doverview.rst27 .. include:: verity.rst
/OK3568_Linux_fs/kernel/drivers/md/
H A DMakefile23 dm-verity-y += dm-verity-target.o
71 obj-$(CONFIG_DM_VERITY) += dm-verity.o
93 dm-verity-objs += dm-verity-fec.o
97 dm-verity-objs += dm-verity-verify-sig.o
H A DKconfig545 be called dm-verity.
555 Add ability for dm-verity device to be validated if the
567 Add forward error correction support to dm-verity. This option
/OK3568_Linux_fs/kernel/Documentation/admin-guide/device-mapper/
H A Ddm-init.rst32 <target_type> ::= "verity" | "linear" | ... (see list below)
61 `verity` allowed
85 dm-verity,,3,ro,
86 0 1638400 verity 1 /dev/sdc1 /dev/sdc2 4096 4096 204800 1 sha256
120 "verity"::
122 dm-verity,,4,ro,
123 0 1638400 verity 1 8:1 8:2 4096 4096 204800 1 sha256
H A Dverity.rst2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
40 dm-verity device.
105 verity <dev> is encrypted the <fec_dev> should be too.
122 rather than every time. This reduces the overhead of dm-verity so that it
142 dm-verity is meant to be set up as part of a verified boot path. This
146 When a dm-verity device is configured, it is expected that the caller
194 The verity kernel code does not read the verity metadata on-disk header.
197 verity header.
222 "0 2097152 verity 1 /dev/sda1 /dev/sda2 4096 4096 262144 1 sha256 "\
H A Dindex.rst36 verity
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-crypto/fsverity-utils/
H A Dfsverity-utils_1.5.bb1 SUMMARY = "Userspace utilities for fs-verity"
2 DESCRIPTION = "fs-verity is a Linux kernel feature that does transparent \
5 mechanism is similar to dm-verity, but implemented at the file level rather \
/OK3568_Linux_fs/kernel/fs/incfs/
H A DMakefile13 incrementalfs-$(CONFIG_FS_VERITY) += verity.o
H A Dvfs.c193 bool verity; member
339 if (search->verity) in inode_set()
375 .verity = read_verity_attr(backing_dentry), in fetch_regular_inode()
/OK3568_Linux_fs/kernel/fs/f2fs/
H A DMakefile10 f2fs-$(CONFIG_FS_VERITY) += verity.o
H A Dsysfs.c784 F2FS_FEATURE_RO_ATTR(verity);
915 ATTR_LIST(verity),
946 F2FS_SB_FEATURE_RO_ATTR(verity, VERITY);
/OK3568_Linux_fs/kernel/fs/ext4/
H A DMakefile19 ext4-$(CONFIG_FS_VERITY) += verity.o
H A Dsysfs.c318 EXT4_ATTR_FEATURE(verity);
335 ATTR_LIST(verity),
H A Dinode.c1306 bool verity = ext4_verity_in_progress(inode); in ext4_write_end() local
1330 if (!verity) in ext4_write_end()
1335 if (old_size < pos && !verity) in ext4_write_end()
1347 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_write_end()
1358 if (pos + len > inode->i_size && !verity) { in ext4_write_end()
1419 bool verity = ext4_verity_in_progress(inode); in ext4_journalled_write_end() local
1451 if (!verity) in ext4_journalled_write_end()
1458 if (old_size < pos && !verity) in ext4_journalled_write_end()
1468 if (pos + len > inode->i_size && !verity && ext4_can_truncate(inode)) in ext4_journalled_write_end()
1478 if (pos + len > inode->i_size && !verity) { in ext4_journalled_write_end()
/OK3568_Linux_fs/kernel/security/loadpin/
H A DKconfig12 dm-verity or a CDROM.
/OK3568_Linux_fs/kernel/Documentation/admin-guide/LSM/
H A DLoadPin.rst8 such as dm-verity or CDROM. This allows systems that have a verified
/OK3568_Linux_fs/kernel/fs/
H A DMakefile39 obj-$(CONFIG_FS_VERITY) += verity/
H A DKconfig116 source "fs/verity/Kconfig"
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Dverified-boot.txt12 memory, then loading a signed kernel, then using the kernel's dm-verity
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-fs-f2fs217 verity, sb_checksum, casefold, readonly, compression, pin_file.
227 verity, sb_checksum, casefold, readonly, compression.
237 inode_crtime, lost_found, verity, sb_checksum,

12