| /openbmc/openbmc-build-scripts/config/gitlint/ |
| H A D | bad_signedoffby.py | 14 violations = []
22 violations.append(
31 violations.append(
40 return violations
|
| /openbmc/linux/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()
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()
|
| H A D | ima_queue.c | 37 .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 | 178 atomic_long_t violations; member
|
| /openbmc/linux/arch/ia64/ |
| H A 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
|
| /openbmc/linux/Documentation/process/ |
| H A 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
|
| /openbmc/linux/drivers/infiniband/hw/qib/ |
| H A D | qib_mad.h | 194 __be16 violations; member
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-filter/ulogd2/ |
| H A D | ulogd2_2.0.8.bb | 4 policy violations) and flow-based logging, e.g. for accounting purpose."
|
| /openbmc/linux/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
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 67 layering violations then the recommended way around that is to wrap ``vmalloc``
|
| /openbmc/qemu/docs/devel/ |
| H A D | conflict-resolution.rst | 8 serious code of conduct violations (including sexist/racist statements
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A 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.
|
| /openbmc/docs/designs/ |
| H A D | bmc-health-monitor.md | 159 …d | Interface to represent Metric thresholds and signals for threshold violations. | Optional …
232 starting systemd services on threshold violations.
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | pamu.txt | 22 interrupt, used for reporting access violations. The second
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | PolyForm-Noncommercial-1.0.0 | 99 and take practical steps to correct past violations, within
|
| H A D | PolyForm-Small-Business-1.0.0 | 89 and take practical steps to correct past violations, within
|
| /openbmc/u-boot/drivers/misc/ |
| H A D | Kconfig | 139 like software violations or hardware security violations.
|
| /openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
| H A D | tripwire.txt | 40 …e Tripwire database after an integrity check if you determine that the violations discovered are v…
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | qapi-schema-test.json | 7 # Whitelists to permit QAPI rule violations
|
| /openbmc/linux/tools/testing/selftests/bpf/ |
| H A D | README.rst | 16 violations of other checks (such as additional warnings being emitted or a
|
| /openbmc/bmcweb/ |
| H A D | DEVELOPING.md | 201 clang-tidy is a tool that can be used to identify coding style violations, bad
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | sysfs-interface.rst | 58 make comparisons of readings to thresholds. This allows violations
|
| /openbmc/docs/ |
| H A D | LICENSE | 330 right the Licensor may have to seek remedies for Your violations
|
| /openbmc/phosphor-logging/docs/ |
| H A D | structured-logging.md | 151 compile warnings about format violations.
|