Searched full:against (Results 1 – 25 of 311) sorted by relevance
12345678910>>...13
| /Documentation/security/tpm/ |
| D | tpm-security.rst | 21 Snooping and Alteration Attacks against the bus
27 successfully demonstrated against the `Windows Bitlocker TPM`_ system.
28 Most recently the same `attack against TPM based Linux disk
72 interception which HMAC protection alone cannot protect against, so
126 collect the name and verifies it against its derived key.
165 of the generated primary key against the one in the certificate (the
206 signature of the returned certifyInfo is verified against the public
214 .. _attack against TPM based Linux disk encryption: https://www.secura.com/blog/tpm-sniffing-attack…
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 7 against and must be installed on the system for applications to work.
30 To build both static libbpf.a and shared libbpf.so against a custom libelf
|
| /Documentation/ |
| D | atomic_t.txt | 180 Where 'unordered' is against other memory locations. Address dependencies are
183 Fully ordered primitives are ordered against everything prior and everything
194 smp_mb__before_atomic() orders all earlier accesses against the RMW op
196 later accesses against the RMW op and all accesses preceding it. However,
226 a RELEASE because it orders preceding instructions against both the read
227 and write parts of the atomic_dec(), and against all following instructions
260 because it would not order the W part of the RMW against the following
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 10 2. Patches should be against kvm.git master branch.
39 12. Features must be robust against reset and kexec - for example, shared
|
| /Documentation/driver-api/media/ |
| D | dtv-common.rst | 43 Two or more readers must be locked against each other.
46 Two or more writers must be locked against each other.
|
| /Documentation/kbuild/ |
| D | headers_install.rst | 19 means that a program built against a C library using older kernel headers
21 features), but a program built against newer kernel headers may not work on an
|
| /Documentation/hwmon/ |
| D | ltc4260.rst | 46 value of the divider resistor against the measured voltage and R2 is the value
47 of the divider resistor against Ground.
|
| D | ltc4261.rst | 46 value of the divider resistor against the measured voltage and R2 is the value
47 of the divider resistor against Ground.
|
| D | ltc2945.rst | 46 value of the divider resistor against the measured voltage and R2 is the value
47 of the divider resistor against Ground.
|
| D | pm6764tr.rst | 31 response. The device assures fast and independent protection against load overcurrent,
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 56 to match a scan handler against each of them using the ids arrays of the
66 interesting to the given scan handler and may be matched against the next scan
79 is the order in which they are matched against device nodes during namespace
|
| /Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 31 - Check against memory allocation failure for SCRIPTZ and add the
33 - Check against GPIO3 pulled low for HVD controllers (driver did
84 - Mask GPCNTL against 0x1c (was 0xfc) for the reading of the NVRAM.
130 - Prepare a new patch against linux-2.4.13.
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 29 Automation runs against this patchwork instance, building/testing patches as
30 they arrive. The automation applies patches against the current HEAD of the
|
| /Documentation/filesystems/ext4/ |
| D | mmp.rst | 7 filesystem against multiple hosts trying to use the filesystem
31 The checksum is calculated against the FS UUID and the MMP structure.
|
| /Documentation/ABI/removed/ |
| D | devfs | 7 against the LSB, and can be replaced by using udev.
|
| /Documentation/filesystems/ |
| D | dlmfs.rst | 56 against raw disks.
83 and write(2) against the fd obtained via your open(2) call. The
94 domain directory. Locking against them is done via the open(2) system
|
| /Documentation/security/ |
| D | self-protection.rst | 6 structures within the Linux kernel to protect against security flaws in
16 but with systems in place that defend against the worst case we'll
18 still be kept in mind, is protecting the kernel against a _privileged_
34 The most fundamental defense against security exploits is to reduce the
135 To protect against even privileged users, systems may need to either
149 kind of attack exist, and protections exist to defend against them.
268 attacks, it is important to defend against exposure of both kernel memory
|
| D | lsm-development.rst | 7 what it tries to protect against and in what cases one would expect to
|
| /Documentation/core-api/ |
| D | assoc_array.rst | 40 problem, the iterator should lock against modification. Objects will not
144 Compare the object against an index key and return ``true`` if it matches and
199 The caller should lock exclusively against other modifiers of the array.
219 The caller should lock exclusively against other modifiers of the array.
235 The caller should lock exclusively against other modifiers of the array.
249 The caller should lock exclusively against other modifiers and accessors
277 lock exclusively against other modifiers of the array.
298 this is a problem, then modification should be locked against. The
544 this without locking against a read - so we have to replace that node too.
|
| D | memory-hotplug.rst | 92 - synchronize against online/offline requests (e.g. via sysfs). This way, memory
96 - synchronize against CPU hotplug and similar (e.g. relevant for ACPI and PPC)
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-table-change.rst | 9 The event interface provides two ioctls to be used against the
|
| /Documentation/admin-guide/cifs/ |
| D | todo.rst | 113 1) check out max path names and max path name components against various server
124 4) More exhaustively test against less common servers
127 against Windows, Samba and Azure currently - to add additional tests and
|
| /Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 114 the callsite to be compared, and a value to compare against. Possible
140 The given string is compared against the function name
147 The given string is compared against either the src-root relative
158 The given string is compared against the module name
184 The given class_name is validated against each module, which may
195 against the line number of each ``pr_debug()`` callsite. A single
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 135 will protect the data against accidental corruption.
157 the size of files that were written. To protect against this
162 modification. To protect against accidental modification, use a
163 crc algorithm, to protect against malicious modification, use a
274 numbers in the journal section, to protect against a
|
| /Documentation/admin-guide/hw-vuln/ |
| D | vmscape.rst | 42 Note that the existing userspace mitigation against Spectre-v2 is effective in
56 vulnerable to cross-thread attacks. For complete protection against VMSCAPE
|
12345678910>>...13