Searched refs:integrity (Results 1 – 25 of 61) sorted by relevance
123
| /linux-3.4.99/Documentation/block/ |
| D | data-integrity.txt | 14 support for appending integrity metadata to an I/O. The integrity
25 DIF and the other integrity extensions is that the protection format
27 integrity of the I/O and reject it if corruption is detected. This
36 allow the operating system to interact with the integrity metadata
42 information to each sector. The data + integrity metadata is stored
49 encouraged them to allow separation of the data and integrity metadata
63 when writing and vice versa. This allows the integrity metadata to be
69 buffers and the integrity metadata. These two distinct buffers must
72 The separation of the data and integrity metadata buffers as well as
81 The data integrity framework in Linux enables protection information
[all …]
|
| /linux-3.4.99/block/ |
| D | blk-integrity.c | 144 struct blk_integrity *b1 = gd1->integrity; in blk_integrity_compare()
145 struct blk_integrity *b2 = gd2->integrity; in blk_integrity_compare()
390 if (disk->integrity == NULL) { in blk_integrity_register()
407 disk->integrity = bi; in blk_integrity_register()
409 bi = disk->integrity; in blk_integrity_register()
438 if (!disk || !disk->integrity) in blk_integrity_unregister()
441 bi = disk->integrity; in blk_integrity_unregister()
446 disk->integrity = NULL; in blk_integrity_unregister()
|
| D | Kconfig | 79 bool "Block layer data integrity support"
83 data integrity option provides hooks which can be used by
84 filesystems to ensure better data integrity.
|
| D | Makefile | 20 obj-$(CONFIG_BLK_DEV_INTEGRITY) += blk-integrity.o
|
| /linux-3.4.99/security/integrity/ |
| D | Makefile | 5 obj-$(CONFIG_INTEGRITY) += integrity.o
8 integrity-y := iint.o
|
| D | Kconfig | 20 source security/integrity/ima/Kconfig
21 source security/integrity/evm/Kconfig
|
| /linux-3.4.99/security/ |
| D | Makefile | 29 subdir-$(CONFIG_INTEGRITY) += integrity
30 obj-$(CONFIG_INTEGRITY) += integrity/built-in.o
|
| D | Kconfig | 103 the TPM bios character driver and IMA, an integrity provider. It is
192 source security/integrity/Kconfig
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-block | 31 What: /sys/block/<disk>/integrity/format
35 Metadata format for integrity capable block device.
39 What: /sys/block/<disk>/integrity/read_verify
44 integrity of read requests serviced by devices that
45 support sending integrity metadata.
48 What: /sys/block/<disk>/integrity/tag_size
52 Number of bytes of integrity tag space available per
56 What: /sys/block/<disk>/integrity/write_generate
62 devices that support receiving integrity metadata.
|
| D | evm | 6 against integrity attacks. The initial method maintains an
|
| /linux-3.4.99/security/integrity/ima/ |
| D | Kconfig | 23 an aggregate integrity value over this list inside the
37 that IMA uses to maintain the integrity aggregate of the
47 at boot. If this option is selected, informational integrity
|
| /linux-3.4.99/fs/btrfs/ |
| D | Kconfig | 36 bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
45 If the integrity check tool is included and activated in
51 to verify the integrity of (super)-block write requests
|
| D | Makefile | 14 btrfs-$(CONFIG_BTRFS_FS_CHECK_INTEGRITY) += check-integrity.o
|
| /linux-3.4.99/Documentation/ |
| D | xz.txt | 15 for integrity checking. The home page of XZ Embedded is at
56 Since the XZ Embedded supports only streams with no integrity check or
57 CRC32, make sure that you don't use some other integrity check type
64 which will verify the integrity of the uncompressed data anyway.
65 Double checking the integrity would probably be waste of CPU cycles.
67 by the decoder; you can only change the integrity check type (or
|
| D | digsig.txt | 13 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
62 * Verifies data integrity against digital signature.
|
| /linux-3.4.99/drivers/scsi/ |
| D | sd_dif.c | 339 "Enabling DIX %s protection\n", disk->integrity->name); in sd_dif_config_host()
344 disk->integrity->tag_size = sizeof(u16) + sizeof(u32); in sd_dif_config_host()
346 disk->integrity->tag_size = sizeof(u16); in sd_dif_config_host()
349 disk->integrity->tag_size); in sd_dif_config_host()
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | jfs.txt | 21 from backup media. The integrity of the volume is not
24 integrity Default. Commit metadata changes to the journal. Use this
|
| /linux-3.4.99/security/integrity/evm/ |
| D | Kconfig | 11 integrity attacks.
|
| /linux-3.4.99/security/smack/ |
| D | Kconfig | 7 Smack is useful for sensitivity, integrity, and a variety
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | verity.txt | 4 Device-Mapper's "verity" target provides transparent integrity checking of
27 This is the device containing data, the integrity of which needs to be
79 Cryptographic hashes are used to assert the integrity of the device on a
115 It is expected that a user-space tool will verify the integrity of the
|
| /linux-3.4.99/Documentation/security/ |
| D | keys-trusted-encrypted.txt | 9 in hex ascii for convenience, and are integrity verified.
13 (integrity measurement) values, and only unsealed by the TPM, if PCRs and blob
14 integrity verifications match. A loaded Trusted Key can be updated with new
|
| /linux-3.4.99/lib/xz/ |
| D | Kconfig | 6 the .xz file format as the container. For integrity checking,
|
| /linux-3.4.99/drivers/md/ |
| D | dm.h | 173 struct dm_md_mempools *dm_alloc_md_mempools(unsigned type, unsigned integrity);
|
| /linux-3.4.99/Documentation/scsi/ |
| D | osd.txt | 88 and signs the request using the provided capability key and integrity-
137 | Out-data integrity |<------/ | | |
148 | In-data integrity |<------------/
|
| /linux-3.4.99/fs/ |
| D | Makefile | 24 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o
|
123