| /linux/security/integrity/ima/ |
| H A D | ima_api.c | 105 int violation, struct inode *inode, in ima_store_template() argument
113 if (!violation) { in ima_store_template()
124 result = ima_add_template_entry(entry, violation, op, inode, filename); in ima_store_template()
144 .violation = cause }; in ima_add_violation()
145 int violation = 1; in ima_add_violation() local
156 result = ima_store_template(entry, violation, inode, in ima_add_violation()
367 int violation = 0; in ima_store_measurement() local
385 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
|
| H A D | ima_queue.c | 166 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_add_template_entry() argument
190 if (!violation && !IS_ENABLED(CONFIG_IMA_DISABLE_HTABLE)) { in ima_add_template_entry()
206 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| H A D | ima_init.c | 54 int violation = 0; in ima_add_boot_aggregate() local
88 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| H A D | ima_template_lib.c | 357 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
414 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
438 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ngv2_init()
467 if (event_data->violation) { in ima_eventdigest_modsig_init()
|
| H A D | ima.h | 77 const char *violation; member
262 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
406 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| H A D | ima_main.c | 1064 int violation = 0; in process_buffer_measurement() local
1136 ret = ima_store_template(entry, violation, NULL, event_data.buf, pcr); in process_buffer_measurement()
|
| /linux/Documentation/process/ |
| H A D | kernel-enforcement-statement.rst | 26 However, if you cease all violation of this License, then your license
30 fails to notify you of the violation by some reasonable means prior to
35 violation by some reasonable means, this is the first time you have
36 received notice of violation of this License (for any work) from that
37 copyright holder, and you cure the violation prior to 30 days after
|
| H A D | code-of-conduct-interpretation.rst | 52 considered a violation report unless you want it to be. If you are
77 rejecting unsuitable contributions are not viewed as a violation of the
82 have to set priorities. This, also, is not to be seen as a violation of
115 addressed now as a violation. Inappropriate language can be seen as a
177 behavior and make amends for it in the setting the violation has taken place.
201 Seek public apology for the violation
205 setting in which the violation has taken place, seeking public apology
206 for the violation.
208 A public apology for the violation is the first step towards rebuilding
212 Remedial measures if there is no public apology for the violation
|
| H A D | embargoed-hardware-issues.rst | 108 effective deterrent in our community. In case a violation happens the
110 or anyone else becomes aware of a potential violation, please report it
|
| /linux/Documentation/networking/device_drivers/ethernet/ti/ |
| H A D | icssg_prueth.rst | 25 …h increments when RTU drops a locally injected packet due to port being disabled or rule violation.
34 …OPPED_PKT``: This counter is incremented when a packet is dropped at PRU because of rule violation.
40 - ``FW_INF_SAV``: Incremented when RX frame is dropped due to Source Address violation
|
| /linux/drivers/soc/mediatek/ |
| H A D | Kconfig | 24 This driver is mainly used to handle the violation which catches
26 The violation information is logged for further analysis or
|
| /linux/lib/ |
| H A D | Kconfig.ubsan | 32 when a UBSAN violation occurs. (Except on arm64 and x86, which
35 out the details of a UBSAN violation. It makes the kernel log
176 In this mode, any UBSAN violation in EL2 would panic the kernel
|
| /linux/drivers/infiniband/hw/hfi1/ |
| H A D | pcie.c | 723 u32 violation; in load_eq_table() local
739 PCIE_CFG_REG_PL105, &violation); in load_eq_table()
746 if (violation in load_eq_table()
|
| /linux/drivers/media/platform/qcom/camss/ |
| H A D | camss-vfe-17x.c | 316 u32 violation = readl_relaxed(vfe->base + VFE_VIOLATION_STATUS); in vfe_violation_read() local
318 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| H A D | camss-vfe-4-1.c | 880 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
882 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| H A D | camss-vfe-4-7.c | 1097 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
1099 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| H A D | camss-vfe-4-8.c | 1087 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
1089 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| /linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 191 To prevent this logic violation all non-owning references are invalidated by the
248 has already been removed as a result of this violation. State 6 is a dangerous
|
| /linux/arch/m68k/ifpsp060/ |
| H A D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-bus-usb | 105 Note that some devices, in violation of the USB spec, have a
|
| /linux/Documentation/arch/x86/ |
| H A D | shstk.rst | 140 violation on the sigreturn path that goes through the restorer.
|
| /linux/Documentation/trace/rv/ |
| H A D | runtime-verification.rst | 90 a violation occurs.
|
| H A D | monitor_synthesis.rst | 191 violation is detected.
|
| /linux/LICENSES/dual/ |
| H A D | CC-BY-4.0 | 337 1. automatically as of the date the violation is cured, provided
339 violation; or
|
| /linux/drivers/memory/ |
| H A D | Kconfig | 167 represents a coherency violation.
|