Searched refs:violations (Results 1 – 21 of 21) sorted by relevance
55 return ima_show_htable_value(buf, count, ppos, &ima_htable.violations); in ima_show_htable_violations()364 static struct dentry *violations; variable485 violations = in ima_fs_init()488 if (IS_ERR(violations)) in ima_fs_init()499 securityfs_remove(violations); in ima_fs_init()
37 .violations = ATOMIC_LONG_INIT(0),
147 atomic_long_inc(&ima_htable.violations); in ima_add_violation()
178 atomic_long_t violations; member
22 bool "Print possible IA-64 dependency violations to console"27 or Write-after-Read (WAR) violations. This option is ignored if you
39 Check for trivial violations with the patch style checker prior to41 You should be able to justify all violations that remain in
180 Check your patch for basic style violations, details of which can be204 You should be able to justify all violations that remain in your
194 __be16 violations; member
67 layering violations then the recommended way around that is to wrap ``vmalloc``
635 violations. If your architecture supports it you can select the "Enable
22 interrupt, used for reporting access violations. The second
117 violations. Unfortunately MCA/INIT start off as massive layer118 violations (can occur at _any_ time) and they build from there.
167 bool "Allow usercopy whitelist violations to fallback to object size"
314 security violations. This also included rtc,
58 make comparisons of readings to thresholds. This allows violations
506 of dropped frames, which is a sum of frames dropped due to timing violations,
1242 This allows rt mutex semantics violations and rt mutex related1259 This feature allows mutex semantics violations to be detected and
289 :c:func:`ata_port_freeze` is called when HSM violations or some other
1186 frames. Such violations are normally logged via a kernel warning.
608 expectation of cache coherence is so deeply ingrained that violations
39 (scripts/checkpatch.pl) to catch trivial style violations.
