Searched refs:violations (Results 1 – 21 of 21) sorted by relevance
60 return ima_show_htable_value(buf, count, ppos, &ima_htable.violations); in ima_show_htable_violations()366 static struct dentry *violations; variable487 violations = in ima_fs_init()490 if (IS_ERR(violations)) in ima_fs_init()501 securityfs_remove(violations); in ima_fs_init()
41 .violations = ATOMIC_LONG_INIT(0),
164 atomic_long_t violations; member
142 atomic_long_inc(&ima_htable.violations); in ima_add_violation()
22 bool "Print possible IA-64 dependency violations to console"27 or Write-after-Read (WAR) violations. This option is ignored if you
35 Check for trivial violations with the patch style checker prior to37 You should be able to justify all violations that remain in
235 Check your patch for basic style violations, details of which can be259 You should be able to justify all violations that remain in your
194 __be16 violations; member
65 layering violations then the recommended way around that is to wrap ``vmalloc``
22 interrupt, used for reporting access violations. The second
113 violations. Unfortunately MCA/INIT start off as massive layer114 violations (can occur at _any_ time) and they build from there.
111 hardware during both bounds violations or when the tables are not189 can get violation address and bounds when bounds violations occur.
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
645 violations. If your architecture supports it you can select the "Enable
1119 This allows rt mutex semantics violations and rt mutex related1136 This feature allows mutex semantics violations to be detected and
289 :c:func:`ata_port_freeze` is called when HSM violations or some other
960 frames. Such violations are normally logged via a kernel warning.
612 expectation of cache coherence is so deeply ingrained that violations
37 (scripts/checkpatch.pl) to catch trivial style violations.
