Searched full:verify (Results 1 – 25 of 183) sorted by relevance
12345678
| /Documentation/admin-guide/device-mapper/ |
| D | dm-init.rst | 45 `cache` constrained, userspace should verify cache device
48 `era` constrained, userspace should verify metadata device
51 `log-writes` constrained, userspace should verify metadata device
52 `mirror` constrained, userspace should verify main/mirror device
53 `raid` constrained, userspace should verify metadata device
54 `snapshot` constrained, userspace should verify src/dst device
56 `snapshot-merge` constrained, userspace should verify src/dst device
58 `switch` constrained, userspace should verify dev path
62 `writecache` constrained, userspace should verify cache device
|
| D | verity.rst | 91 Do not verify blocks that are expected to contain zeroes and always return
121 Verify data blocks only the first time they are read from the data device,
146 verify data blocks in bottom half instead of workqueue. This option can
212 It is expected that a user-space tool will verify the integrity of the
242 A command line tool veritysetup is available to compute or verify
|
| D | log-writes.rst | 7 to verify the integrity of metadata or data as the file system is written to.
122 <verify md5sum's are correct>
124 Another option is to do a complicated file system operation and verify the file
|
| /Documentation/ |
| D | Kconfig | 22 scripts/get_abi.pl. Add a check to verify them.
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 21 PVM, decrypt the components and verify the data and address list
57 decrypt and verify the PV, as well as control flags and a start PSW.
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 67 need to verify that you are using a reasonably recent version of it.
168 is what you will have. You can verify by running ``gpg --list-secret-keys``,
432 any modern Linux workstation. You can verify it by running::
571 To verify that the smartcard is working as intended, you can create a
575 $ gpg --verify /tmp/test.asc
578 show "Good signature" after you run ``gpg --verify``.
655 hundreds of cloned repositories floating around, how does anyone verify
693 How to verify signed tags
696 To verify a signed tag, simply use the ``verify-tag`` command::
698 $ git verify-tag [tagname]
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-intel.rst | 55 6) Verify the backup::
73 9) Verify that the new content of the SPI serial flash matches the new
|
| /Documentation/devicetree/bindings/soc/litex/ |
| D | litex,soc-controller.yaml | 12 Its purpose is to verify LiteX CSR (Control&Status Register) access
|
| /Documentation/filesystems/ext4/ |
| D | eainode.rst | 17 inode is not referenced by multiple inodes) to verify that the EA inode
|
| /Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 19 1.3 verify
50 .verify - A pointer to a "verification" function.
123 | | cpufreq_driver.verify and either |
139 1.3 verify
258 are met. This is helpful for the ->verify call.
|
| /Documentation/devicetree/bindings/misc/ |
| D | xlnx,tmr-inject.yaml | 15 possibility to verify that the TMR subsystem error detection and fault
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,trace-buffer-extension.yaml | 16 accessed via CPU system registers. The software can verify
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 28 ``CONFIG_KEXEC_VERIFY_SIG`` to verify kernel module and kernel image while
|
| /Documentation/kbuild/ |
| D | reproducible-builds.rst | 7 exactly the same. This makes it possible to verify that the build
9 been subverted. This can also make it easier to verify that a source
|
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 271 name: verify-enabled
274 name: verify-status
277 name: verify-time
280 name: max-verify-time
1889 - verify-enabled
1890 - verify-time
1891 - max-verify-time
1904 - verify-enabled
1905 - verify-time
|
| /Documentation/driver-api/thermal/ |
| D | x86_pkg_temperature_thermal.rst | 9 (Verify using: CPUID.06H:EAX[bit 6] =1)
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 22 verify, and this in turn limits the supportable size of an XFS filesystem.
66 hence parse and verify the metadata object. IF we can't independently identify
80 integrity checking. We cannot trust the metadata if we cannot verify that it has
83 block. If we can verify the block contains the metadata it was intended to
324 This will verify the internal structure of the metadata before we go any
|
| /Documentation/translations/zh_CN/core-api/ |
| D | workqueue.rst | 397 --name=iops-test-job --verify=sha512
399 这里有24个发起者，每个同时发起64个IO。 ``--verify=sha512``
436 --time_based --group_reporting --name=iops-test-job --verify=sha512
477 --time_based --group_reporting --name=iops-test-job --verify=sha512
|
| /Documentation/arch/x86/ |
| D | intel_txt.rst | 127 verify the kernel and initrd.
183 will re-calculate the MAC and verify it against the sealed value.
222 DRTM process to verify and configure the system. It is signed
|
| /Documentation/networking/device_drivers/ethernet/neterion/ |
| D | s2io.rst | 157 b. Ensure Transmit Checksum offload is enabled. Use ethtool to set/verify this
177 set/verify this option.
|
| /Documentation/filesystems/ |
| D | bfs.rst | 50 Just in case, you can verify that you have done the right thing by checking
|
| D | directory-locking.rst | 60 * verify that the source is not a descendent of the target and
95 First of all, we verify that it is *not* an ancestor of our directory
160 It's easy to verify that operations never take a lock with rank
|
| /Documentation/admin-guide/ |
| D | index.rst | 41 verify-bugs-and-bisect-regressions
|
| D | filesystem-monitoring.rst | 18 to verify an IO operation was successfully executed. That is out of
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 56 architectures may need to verify that code has been compiled in a manner
60 with such requirements should verify the kernel compilation using
89 architectures verify that a stacktrace ends at an expected location, e.g.
|
12345678