| /Linux-v5.15/security/integrity/ima/ |
| D | ima_api.c | 103 int violation, struct inode *inode, in ima_store_template() argument
111 if (!violation) { in ima_store_template()
122 result = ima_add_template_entry(entry, violation, op, inode, filename); in ima_store_template()
142 .violation = cause }; in ima_add_violation()
143 int violation = 1; in ima_add_violation() local
154 result = ima_store_template(entry, violation, inode, in ima_add_violation()
317 int violation = 0; in ima_store_measurement() local
335 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
|
| D | ima_queue.c | 159 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_add_template_entry() argument
171 if (!violation && !IS_ENABLED(CONFIG_IMA_DISABLE_HTABLE)) { in ima_add_template_entry()
187 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| D | ima_init.c | 51 int violation = 0; in ima_add_boot_aggregate() local
89 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| D | ima.h | 69 const char *violation; member
139 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
281 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| D | ima_template_lib.c | 321 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
377 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
403 if (event_data->violation) { in ima_eventdigest_modsig_init()
|
| D | ima_main.c | 883 int violation = 0; in process_buffer_measurement() local
955 ret = ima_store_template(entry, violation, NULL, event_data.buf, pcr); in process_buffer_measurement()
|
| /Linux-v5.15/Documentation/process/ |
| 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
|
| 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
|
| D | embargoed-hardware-issues.rst | 108 effective deterrent in our community. In case a violation happens the
110 or anyone becomes aware of a potential violation, please report it
|
| D | 1.Intro.rst | 196 a result, their distribution is a violation of the GNU General Public
|
| /Linux-v5.15/drivers/soc/mediatek/ |
| 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-v5.15/drivers/infiniband/hw/hfi1/ |
| D | pcie.c | 730 u32 violation; in load_eq_table() local
746 PCIE_CFG_REG_PL105, &violation); in load_eq_table()
753 if (violation in load_eq_table()
|
| /Linux-v5.15/drivers/media/platform/qcom/camss/ |
| D | camss-vfe-170.c | 336 u32 violation = readl_relaxed(vfe->base + VFE_VIOLATION_STATUS); in vfe_violation_read() local
338 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| D | camss-vfe-4-1.c | 883 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
885 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| D | camss-vfe-4-7.c | 1146 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
1148 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| D | camss-vfe-4-8.c | 1130 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
1132 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| /Linux-v5.15/arch/m68k/ifpsp060/ |
| D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-bus-usb | 105 Note that some devices, in violation of the USB spec, have a
|
| /Linux-v5.15/drivers/base/firmware_loader/ |
| D | Kconfig | 59 then it may be a violation of the GPL to distribute the resulting
|
| /Linux-v5.15/drivers/memory/ |
| D | Kconfig | 168 represents a coherency violation.
|
| /Linux-v5.15/LICENSES/dual/ |
| D | CC-BY-4.0 | 337 1. automatically as of the date the violation is cured, provided
339 violation; or
|
| /Linux-v5.15/arch/arm64/boot/dts/qcom/ |
| D | sdm845-oneplus-common.dtsi | 56 * rmtfs_mem region to trigger an XPU violation, causing a crash.
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | debugfs-driver-habanalabs | 197 Description: Check and display page fault or access violation mmu errors for
|
| /Linux-v5.15/Documentation/driver-api/usb/ |
| D | URB.rst | 191 cause a memory-access violation. The driver is responsible for avoiding this,
|
| /Linux-v5.15/Documentation/block/ |
| D | data-integrity.rst | 102 concept of an end-to-end protection scheme is a layering violation.
|
