Searched refs:violations (Results 1 – 24 of 24) sorted by relevance
| /Linux-v6.6/security/integrity/ima/ |
| D | ima_fs.c | 55 return ima_show_htable_value(buf, count, ppos, &ima_htable.violations); in ima_show_htable_violations()
364 static struct dentry *violations; variable
495 violations = in ima_fs_init()
498 if (IS_ERR(violations)) { in ima_fs_init()
499 ret = PTR_ERR(violations); in ima_fs_init()
514 securityfs_remove(violations); in ima_fs_init()
|
| D | ima_queue.c | 37 .violations = ATOMIC_LONG_INIT(0),
|
| D | ima_api.c | 147 atomic_long_inc(&ima_htable.violations); in ima_add_violation()
|
| D | ima.h | 178 atomic_long_t violations; member
|
| /Linux-v6.6/arch/ia64/ |
| D | Kconfig.debug | 22 bool "Print possible IA-64 dependency violations to console"
27 or Write-after-Read (WAR) violations. This option is ignored if you
|
| /Linux-v6.6/Documentation/process/ |
| D | submit-checklist.rst | 39 Check for trivial violations with the patch style checker prior to
41 You should be able to justify all violations that remain in
|
| D | submitting-patches.rst | 204 Check your patch for basic style violations, details of which can be
227 You should be able to justify all violations that remain in your
|
| /Linux-v6.6/drivers/infiniband/hw/qib/ |
| D | qib_mad.h | 194 __be16 violations; member
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | debugfs-driver-habanalabs | 124 Description: Dumps all security violations to dmesg. This will also ack
125 all security violations meanings those violations will not be
|
| /Linux-v6.6/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 67 layering violations then the recommended way around that is to wrap ``vmalloc``
|
| D | dma-api.rst | 718 violations. If your architecture supports it you can select the "Enable
|
| /Linux-v6.6/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pamu.txt | 22 interrupt, used for reporting access violations. The second
|
| /Linux-v6.6/Documentation/arch/ia64/ |
| D | mca.rst | 117 violations. Unfortunately MCA/INIT start off as massive layer
118 violations (can occur at _any_ time) and they build from there.
|
| /Linux-v6.6/tools/testing/selftests/bpf/ |
| D | README.rst | 16 violations of other checks (such as additional warnings being emitted or a
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | sysfs-interface.rst | 58 make comparisons of readings to thresholds. This allows violations
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | checkpatch.rst | 8 style violations in patches and optionally corrects them. Checkpatch can
12 messages. If your code looks better with the violations, then its probably
|
| /Linux-v6.6/LICENSES/dual/ |
| D | CC-BY-4.0 | 344 right the Licensor may have to seek remedies for Your violations
|
| /Linux-v6.6/Documentation/networking/dsa/ |
| D | sja1105.rst | 292 of dropped frames, which is a sum of frames dropped due to timing violations,
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 204 because doing otherwise prevents KCSAN from detecting violations of your
|
| D | explanation.txt | 661 expectation of cache coherence is so deeply ingrained that violations
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | libata.rst | 265 :c:func:`ata_port_freeze` is called when HSM violations or some other
|
| /Linux-v6.6/arch/ |
| D | Kconfig | 823 When selected, Control Flow Integrity (CFI) violations result in a
|
| /Linux-v6.6/lib/ |
| D | Kconfig.debug | 1383 This allows rt mutex semantics violations and rt mutex related
1400 This feature allows mutex semantics violations to be detected and
|
| /Linux-v6.6/Documentation/networking/ |
| D | ip-sysctl.rst | 1468 frames. Such violations are normally logged via a kernel warning.
|
