| /linux-6.15/security/integrity/ima/ |
| H A D | ima_fs.c | 55 return ima_show_htable_value(buf, count, ppos, &ima_htable.violations); in ima_show_htable_violations()
402 static struct dentry *violations; variable
601 violations = in ima_fs_init()
604 if (IS_ERR(violations)) { in ima_fs_init()
605 ret = PTR_ERR(violations); in ima_fs_init()
620 securityfs_remove(violations); in ima_fs_init()
|
| H A D | ima_queue.c | 38 .violations = ATOMIC_LONG_INIT(0),
|
| H A D | ima_api.c | 147 atomic_long_inc(&ima_htable.violations); in ima_add_violation()
|
| H A D | ima.h | 296 atomic_long_t violations; member
|
| /linux-6.15/Documentation/process/ |
| H A D | submit-checklist.rst | 66 1) Check for trivial violations with the patch style checker prior to
68 You should be able to justify all violations that remain in
|
| H A D | code-of-conduct-interpretation.rst | 242 not taking action when such serious public violations occur.
|
| H A 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-6.15/drivers/infiniband/hw/qib/ |
| H A D | qib_mad.h | 194 __be16 violations; member
|
| /linux-6.15/Documentation/devicetree/bindings/crypto/ |
| H A D | fsl,sec-v4.0-mon.yaml | 18 violations. This also included rtc, system power off and ON/OFF key.
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A 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-6.15/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 69 violations then the recommended way around that (on pre-v5.17 kernels) is to
|
| H A D | dma-api.rst | 718 violations. If your architecture supports it you can select the "Enable
|
| /linux-6.15/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pamu.txt | 22 interrupt, used for reporting access violations. The second
|
| /linux-6.15/Documentation/gpu/ |
| H A D | drm-vm-bind-locking.rst | 111 lists are manipulated. However, to avoid locking order violations
128 over the gpu_vm_bo and gpu_vma lists to avoid locking-order violations.
477 reclaim context and, again, to avoid locking order violations, we can't
|
| /linux-6.15/Documentation/wmi/ |
| H A D | driver-development-guide.rst | 182 violations, you can invoke it with the following command:
|
| /linux-6.15/tools/testing/selftests/bpf/ |
| H A D | README.rst | 16 violations of other checks (such as additional warnings being emitted or a
|
| /linux-6.15/Documentation/userspace-api/fwctl/ |
| H A D | fwctl.rst | 241 The kernel remains the gatekeeper for this interface. If violations of the
|
| /linux-6.15/Documentation/hwmon/ |
| H A D | sysfs-interface.rst | 58 make comparisons of readings to thresholds. This allows violations
|
| /linux-6.15/Documentation/dev-tools/ |
| H A 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-6.15/LICENSES/dual/ |
| H A D | CC-BY-4.0 | 344 right the Licensor may have to seek remedies for Your violations
|
| /linux-6.15/Documentation/networking/ |
| H A D | j1939.rst | 614 failures, protocol violations, or other issues that occur during J1939
802 reason for the abort, such as protocol violations or timeouts.
|
| /linux-6.15/Documentation/networking/dsa/ |
| H A D | sja1105.rst | 292 of dropped frames, which is a sum of frames dropped due to timing violations,
|
| /linux-6.15/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 210 because doing otherwise prevents KCSAN from detecting violations of your
|
| /linux-6.15/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 318 checked and policy violations are logged, but the policy is not really
|
| /linux-6.15/Documentation/driver-api/ |
| H A D | libata.rst | 265 :c:func:`ata_port_freeze` is called when HSM violations or some other
|