/linux-4.1.27/security/integrity/ |
D | Makefile | 5 obj-$(CONFIG_INTEGRITY) += integrity.o 7 integrity-y := iint.o 8 integrity-$(CONFIG_INTEGRITY_AUDIT) += integrity_audit.o 9 integrity-$(CONFIG_INTEGRITY_SIGNATURE) += digsig.o 10 integrity-$(CONFIG_INTEGRITY_ASYMMETRIC_KEYS) += digsig_asymmetric.o
|
D | Kconfig | 7 This option enables the integrity subsystem, which is comprised 45 bool "Enables integrity auditing support " 49 In addition to enabling integrity auditing support, this 51 controls the level of integrity auditing messages. 52 0 - basic integrity auditing messages (default) 53 1 - additional integrity auditing messages 55 Additional informational integrity auditing messages would 59 source security/integrity/ima/Kconfig 60 source security/integrity/evm/Kconfig
|
/linux-4.1.27/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 …]
|
D | 00-INDEX | 11 data-integrity.txt 12 - Block data integrity
|
D | biovecs.txt | 38 advances the bio integrity's iter if present. 41 a pointer to a biovec, not a bio; this is used by the bio integrity code.
|
D | writeback_cache_control.txt | 13 a data integrity operation like fsync, sync or an unmount.
|
D | queue-sysfs.txt | 56 When read, this file shows the max limit of integrity segments as
|
/linux-4.1.27/drivers/scsi/ |
D | sd_dif.c | 65 disk->integrity->flags |= BLK_INTEGRITY_IP_CHECKSUM; in sd_dif_config_host() 73 "Enabling DIX %s protection\n", disk->integrity->name); in sd_dif_config_host() 78 disk->integrity->flags |= BLK_INTEGRITY_DEVICE_CAPABLE; in sd_dif_config_host() 84 disk->integrity->tag_size = sizeof(u16) + sizeof(u32); in sd_dif_config_host() 86 disk->integrity->tag_size = sizeof(u16); in sd_dif_config_host() 89 disk->integrity->tag_size); in sd_dif_config_host()
|
/linux-4.1.27/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 76 prompt "Default integrity hash algorithm" 81 list, integrity appraisal and audit log. The compiled default 111 bool "Appraise integrity measurements" 115 This option enables local measurement integrity appraisal. 121 For more information on integrity appraisal refer to:
|
/linux-4.1.27/block/ |
D | blk-integrity.c | 148 struct blk_integrity *b1 = gd1->integrity; in blk_integrity_compare() 149 struct blk_integrity *b2 = gd2->integrity; in blk_integrity_compare() 422 if (disk->integrity == NULL) { in blk_integrity_register() 439 disk->integrity = bi; in blk_integrity_register() 441 bi = disk->integrity; in blk_integrity_register() 471 if (!disk || !disk->integrity) in blk_integrity_unregister() 476 bi = disk->integrity; in blk_integrity_unregister() 481 disk->integrity = NULL; in blk_integrity_unregister()
|
D | Makefile | 24 obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o t10-pi.o
|
D | Kconfig | 79 bool "Block layer data integrity support" 84 data integrity option provides hooks which can be used by 85 filesystems to ensure better data integrity.
|
/linux-4.1.27/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/device_is_integrity_capable 61 integrity metadata. Set if the device is T10 PI-capable. 64 What: /sys/block/<disk>/integrity/write_generate [all …]
|
D | evm | 6 against integrity attacks. The initial method maintains an
|
/linux-4.1.27/security/ |
D | Makefile | 28 subdir-$(CONFIG_INTEGRITY) += integrity 29 obj-$(CONFIG_INTEGRITY) += integrity/
|
D | Kconfig | 38 the TPM bios character driver and IMA, an integrity provider. It is 127 source security/integrity/Kconfig
|
/linux-4.1.27/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.
|
D | intel_txt.txt | 55 measure or protect the integrity of a running kernel, they all 161 In order to preserve system integrity across S3, the kernel
|
D | vfio.txt | 41 greatest risk to the overall system integrity.
|
D | kernel-parameters.txt | 1122 current integrity status. 1385 ima_appraise= [IMA] appraise integrity measurements 1463 0 -- basic integrity auditing messages. (Default) 1464 1 -- additional integrity auditing messages.
|
/linux-4.1.27/fs/btrfs/ |
D | Kconfig | 45 bool "Btrfs with integrity check tool compiled in (DANGEROUS)" 54 If the integrity check tool is included and activated in 60 to verify the integrity of (super)-block write requests
|
D | Makefile | 15 btrfs-$(CONFIG_BTRFS_FS_CHECK_INTEGRITY) += check-integrity.o
|
/linux-4.1.27/Documentation/filesystems/ |
D | btrfs.txt | 59 These debugging options control the behavior of the integrity checking 62 check_int enables the integrity checker module, which examines all 66 check_int_data includes extent data in the integrity checks, and 70 as defined in fs/btrfs/check-integrity.c, to control the integrity 73 See comments at the top of fs/btrfs/check-integrity.c for more info.
|
D | jfs.txt | 22 from backup media. The integrity of the volume is not 25 integrity(*) Commit metadata changes to the journal. Use this option to
|
D | xfs-self-describing-metadata.txt | 76 integrity checking. We cannot trust the metadata if we cannot verify that it has 78 integrity check, and this is done by adding CRC32c validation to the metadata 85 fast. So while CRC32c is not the strongest of possible integrity checks that 87 little overhead. Adding support for larger integrity fields and/or algorithms 89 complexity and so there is no provision for changing the integrity checking
|
D | logfs.txt | 213 Partial segments may be written for data integrity, but where possible
|
D | xfs.txt | 57 writes into the journal and for data integrity operations.
|
D | xfs-delayed-logging-design.txt | 135 need to ensure application level data integrity is maintained. 276 transactional integrity (as discussed in the next section) so the ordering is
|
D | vfs.txt | 606 This may happen for data integrity reasons (i.e. 'sync'), or
|
/linux-4.1.27/Documentation/device-mapper/ |
D | verity.txt | 4 Device-Mapper's "verity" target provides transparent integrity checking of 28 This is the device containing data, the integrity of which needs to be 96 Cryptographic hashes are used to assert the integrity of the device on a 132 It is expected that a user-space tool will verify the integrity of the
|
D | log-writes.txt | 6 to verify the integrity of metadata or data as the file system is written to.
|
/linux-4.1.27/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-4.1.27/security/integrity/evm/ |
D | Kconfig | 10 integrity attacks.
|
/linux-4.1.27/lib/xz/ |
D | Kconfig | 6 the .xz file format as the container. For integrity checking,
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | rpc-server-gss.txt | 33 - integrity/privacy protection (signing and encrypting of individual 39 Therefore, we perform per-packet integrity and privacy protection in the
|
/linux-4.1.27/security/smack/ |
D | Kconfig | 11 Smack is useful for sensitivity, integrity, and a variety
|
/linux-4.1.27/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 |<------------/
|
D | ChangeLog.sym53c8xx | 124 - Small fix to integrity checking code. 125 - Removed requirement for integrity checking if want to run 193 - Added capability to use the integrity checking code
|
D | LICENSE.qla4xxx | 229 integrity of the free software distribution system, which is
|
D | scsi_eh.txt | 431 it should perform SCSI EH maintenance chores to maintain integrity of
|
D | LICENSE.qla2xxx | 230 integrity of the free software distribution system, which is
|
D | ChangeLog.ncr53c8xx | 109 - Added capability to use the integrity checking code
|
D | ncr53c8xx.txt | 826 0x4: Disable SCSI bus integrity checking.
|
/linux-4.1.27/drivers/md/ |
D | dm.h | 226 unsigned integrity, unsigned per_bio_data_size);
|
D | dm.c | 3536 unsigned integrity, unsigned per_bio_data_size) in dm_alloc_md_mempools() argument 3582 if (integrity && bioset_integrity_create(pools->bs, pool_size)) in dm_alloc_md_mempools()
|
/linux-4.1.27/Documentation/DocBook/ |
D | .kernel-api.xml.cmd | 2 …k/blk-flush.c block/blk-lib.c block/blk-tag.c block/blk-tag.c block/blk-integrity.c kernel/trace/b…
|
/linux-4.1.27/drivers/block/ |
D | nvme-core.c | 525 ts = ns->disk->integrity->tuple_size; in nvme_dif_remap() 553 struct blk_integrity integrity; in nvme_init_integrity() local 557 integrity = t10_pi_type3_crc; in nvme_init_integrity() 561 integrity = t10_pi_type1_crc; in nvme_init_integrity() 564 integrity = nvme_meta_noop; in nvme_init_integrity() 567 integrity.tuple_size = ns->ms; in nvme_init_integrity() 568 blk_integrity_register(ns->disk, &integrity); in nvme_init_integrity()
|
/linux-4.1.27/Documentation/networking/ |
D | generic-hdlc.txt | 85 t391 - link integrity verification polling timer (in seconds) - user
|
D | LICENSE.qlge | 228 integrity of the free software distribution system, which is
|
D | LICENSE.qlcnic | 228 integrity of the free software distribution system, which is
|
D | ppp_generic.txt | 196 to ensure their integrity. As part of this, the generic layer
|
D | bonding.txt | 25 Additionally, link integrity monitoring may be performed.
|
/linux-4.1.27/Documentation/early-userspace/ |
D | buffer-format.txt | 78 significantly stronger integrity check), however, this is the
|
/linux-4.1.27/Documentation/input/ |
D | elantech.txt | 122 Hardware version 1 provides basic data integrity verification by 134 this integrity check, even though it is not an actual cyclic redundancy 137 Depending on the state of crc_enabled, certain basic data integrity
|
/linux-4.1.27/scripts/ |
D | spelling.txt | 518 integrety||integrity 519 integrey||integrity
|
/linux-4.1.27/arch/arm/boot/dts/ |
D | exynos5420-peach-pit.dts | 882 /* Drive SPI lines at x2 for better integrity */ 887 /* Drive SPI chip select at x2 for better integrity */
|
D | exynos5800-peach-pi.dts | 845 /* Drive SPI lines at x2 for better integrity */ 850 /* Drive SPI chip select at x2 for better integrity */
|
/linux-4.1.27/include/linux/ |
D | blkdev.h | 1505 return bdev->bd_disk->integrity; in bdev_get_integrity() 1510 return disk->integrity; in blk_get_integrity()
|
D | genhd.h | 200 struct blk_integrity *integrity; member
|
/linux-4.1.27/Documentation/power/ |
D | userland-swsusp.txt | 138 means, such as checksums, to ensure the integrity of the snapshot image.
|
/linux-4.1.27/lib/ |
D | Kconfig | 88 SCSI data integrity subsystem.
|
/linux-4.1.27/Documentation/hwmon/ |
D | it87 | 251 control mode. The driver will perform basic integrity checks before
|
/linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
D | fsl-sec4.txt | 239 perform run-time integrity check of memory areas that should not modified.
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | cachefiles.txt | 41 The filesystem and data integrity of the cache are only as good as those of the
|
/linux-4.1.27/tools/usb/usbip/ |
D | COPYING | 218 integrity of the free software distribution system, which is
|
/linux-4.1.27/drivers/staging/rtl8192e/ |
D | license | 219 integrity of the free software distribution system, which is implemented
|
/linux-4.1.27/drivers/staging/rtl8192u/ |
D | copying | 218 integrity of the free software distribution system, which is
|
/linux-4.1.27/ |
D | COPYING | 234 integrity of the free software distribution system, which is
|
D | MAINTAINERS | 3918 F: security/integrity/evm/ 5046 F: security/integrity/ima/
|
/linux-4.1.27/Documentation/cdrom/ |
D | cdrom-standard.tex | 642 scheme, some \cdrom\ drivers don't do any integrity checking, resulting 650 fact. An integrity check on opening of the device, that verifies the
|
/linux-4.1.27/arch/blackfin/ |
D | Kconfig | 1266 frequency of about 3.3 MHz. To preserve data integrity in the SDRAM,
|
/linux-4.1.27/crypto/ |
D | Kconfig | 460 Michael MIC is used for message integrity protection in TKIP
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | CHANGES | 612 Fix caching data integrity bug when extending file size especially when no
|