| /linux/tools/memory-model/scripts/ |
| H A D | README | 11 the results against the expected results recorded in the
29 Check a single litmus test against its "Result:" expected result.
34 Check the specified list of litmus tests against their "Result:"
55 against the .litmus file's "Result:" comment to judge whether
97 # Checks results against Result tags, runs in minutes:
|
| /linux/security/ipe/ |
| H A D | eval.c | 126 * evaluate_dmv_roothash() - Evaluate @ctx against a dmv roothash property.
152 * evaluate_dmv_sig_false() - Evaluate @ctx against a dmv sig false property.
165 * evaluate_dmv_sig_true() - Evaluate @ctx against a dmv sig true property.
190 * evaluate_fsv_digest() - Evaluate @ctx against a fsv digest property.
229 * evaluate_fsv_sig_false() - Evaluate @ctx against a fsv sig false property.
245 * evaluate_fsv_sig_true() - Evaluate @ctx against a fsv sig true property.
269 * evaluate_property() - Analyze @ctx against a rule property.
306 * ipe_evaluate_event() - Analyze @ctx against the current active policy.
309 * This is the loop where all policy evaluations happen against the IPE policy.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 12 all of the CPU's prior operations against some or all of its
16 against some or all of the CPU's prior accesses or some or all
68 accesses against all subsequent accesses from the viewpoint of all CPUs.
119 typically instead used to provide ordering against RCU read-side critical
263 end in _release. These operations order their own store against all
287 against "y". On x86, the version using smp_store_release() might compile
307 Note that release ordering is guaranteed only against the
308 memory-store portion of the RMW operation, and not against the
322 operations order their own load against all of the CPU's subsequent
333 improves upon smp_rmb() by ordering against subsequent stores as well
[all …]
|
| H A D | control-dependencies.txt | 192 WRITE_ONCE(c, 1); /* BUG: No ordering against the read from "a". */
219 (*) Control dependencies can order prior loads against later stores.
221 Not prior loads against later loads, nor prior stores against
254 need all the CPUs to agree on the ordering of a given store against
|
| /linux/Documentation/security/tpm/ |
| H A 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…
|
| /linux/security/apparmor/ |
| H A D | match.c | 456 * @dfa: the dfa to match @str against (NOT NULL)
458 * @str: the string of bytes to match against the dfa (NOT NULL)
461 * aa_dfa_match_len will match @str against the dfa and return the state it
505 * @dfa: the dfa to match @str against (NOT NULL)
507 * @str: the null terminated string of bytes to match against the dfa (NOT NULL)
509 * aa_dfa_match will match @str against the dfa and return the state it
598 * @dfa: the dfa to match @str against (NOT NULL)
600 * @str: the null terminated string of bytes to match against the dfa (NOT NULL)
603 * aa_dfa_match will match @str against the dfa and return the state it
655 * @dfa: the dfa to match @str against (NOT NULL)
[all …]
|
| /linux/drivers/rapidio/ |
| H A D | rio-driver.c | 19 * @id: the RIO device id structure to match against
20 * @rdev: the RIO device structure to match against
79 * @dev: the RIO device structure to match against
109 * @dev: the RIO device structure to match against
181 * @dev: the standard device structure to match against
182 * @drv: the standard driver structure containing the ids to match against
|
| /linux/Documentation/ |
| H A 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
|
| /linux/drivers/staging/iio/Documentation/ |
| H A D | inkernel.txt | 18 matched against the datasheet_name field of the iio_chan_spec.
44 * matching dev or dev_name against consumer_dev and consumer_dev_name
45 * matching consumer_channel against consumer_channel in the map
|
| /linux/fs/verity/ |
| H A D | Kconfig | 18 against the Merkle tree. The file is also made read-only.
25 against a known good value, e.g. from a digital signature).
30 protection against malicious disks vs. an ahead-of-time hash.
|
| /linux/drivers/rtc/ |
| H A D | test_rtc_lib.c | 33 * against the expected result.
76 * against the expected result.
85 * against the expected result.
|
| /linux/include/linux/device-id/ |
| H A D | pcmcia.h | 40 /* not matched against in kernelspace */
43 /* not matched against */
|
| H A D | usb.h | 26 * match against new devices. Any field except for driver_info may be
71 /* which fields to match against? */
93 /* not matched against */
|
| /linux/Documentation/scsi/ |
| H A 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.
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | intel_cpu_info.c | 29 * intel_match_g8_cpu - match current CPU against g8_cpu_ids
31 * This matches current CPU against g8_cpu_ids, which are applicable
|
| /linux/Documentation/security/ |
| H A 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
|
| /linux/crypto/asymmetric_keys/ |
| H A D | restrict.c | 63 * Check the new certificate against the ones in the trust keyring. If one of
167 * the new certificate against the ones in the trust_keyring.
267 * available, auth_ids[2] is matched against in key_or_keyring_common()
321 * Check the new certificate only against the key or keys passed in the data
348 * Check the new certificate against the key or keys passed in the data
349 * parameter and against the keys already linked to the destination keyring. If
|
| /linux/tools/testing/selftests/drivers/net/ |
| H A D | README.rst | 14 against software drivers such as netdevsim. No extra preparation is required
22 Executing tests against a real device requires external preparation.
23 The netdevice against which tests will be run must exist, be running
27 the tests against a real device.
36 All tests in drivers/net must support running both against a software device
65 Name of the netdevice against which the test should be executed.
|
| /linux/Documentation/bpf/libbpf/ |
| H A 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
|
| /linux/fs/zonefs/ |
| H A D | zonefs.h | 91 * To serialise fully against both syscall and mmap based IO and
93 * zonefs_seq_file_truncate() against zonefs_iomap_begin(), that is,
94 * file truncate operations against block mapping, i_truncate_mutex is
95 * used. i_truncate_mutex also protects against concurrent accesses
|
| /linux/Documentation/driver-api/acpi/ |
| H A 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
|
| /linux/tools/testing/ktest/examples/ |
| H A D | README | 10 crosstests.conf - this config shows an example of testing a git repo against
22 snowball.conf - An example config that was used to demo ktest.pl against
|
| /linux/Documentation/process/ |
| H A D | threat-model.rst | 5 protect against. These assumptions tend to cause confusion for bug reports
213 Drivers are implemented against a specification. When a device or a storage
214 medium violates the specification its driver was written against, the
216 unless the driver is specifically documented as being hardened against
234 configured with technologies meant to defend against such attacks
|
| /linux/arch/riscv/mm/ |
| H A D | physaddr.c | 12 * Boundary checking against the kernel linear mapping space. in __virt_to_phys()
28 * Boundary checking against the kernel image mapping. in __phys_addr_symbol()
|
| /linux/Documentation/core-api/ |
| H A 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
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
554 this without locking against a read - so we have to replace that node too.
|