Searched refs:violations (Results 1 – 17 of 17) sorted by relevance
44 return ima_show_htable_value(buf, count, ppos, &ima_htable.violations); in ima_show_htable_violations()296 static struct dentry *violations; variable379 violations = in ima_fs_init()382 if (IS_ERR(violations)) in ima_fs_init()394 securityfs_remove(violations); in ima_fs_init()
36 .violations = ATOMIC_LONG_INIT(0),
120 atomic_long_t violations; member
140 atomic_long_inc(&ima_htable.violations); in ima_add_violation()
24 bool "Print possible IA-64 dependency violations to console"29 or Write-after-Read (WAR) violations. This option is ignored if you
30 Documentation/CodingStyle. Check for trivial violations with the32 You should be able to justify all violations that remain in
237 Check your patch for basic style violations, details of which can be259 You should be able to justify all violations that remain in your
587 violations. If your architecture supports it you can select the "Enable
325 __be16 violations; member
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.
291 security violations.
58 make comparisons of readings to thresholds. This allows violations
911 This allows rt mutex semantics violations and rt mutex related934 This feature allows mutex semantics violations to be detected and
854 frames. Such violations are normally logged via a kernel warning.
37 (scripts/checkpatch.pl) to catch trivial style violations.