| /Linux-v5.10/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()
313 int violation = 0; in ima_store_measurement() local
331 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) { in ima_add_template_entry()
186 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| D | ima_init.c | 49 int violation = 0; in ima_add_boot_aggregate() local
87 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| D | ima_template_lib.c | 280 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
336 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
362 if (event_data->violation) { in ima_eventdigest_modsig_init()
|
| D | ima.h | 70 const char *violation; member
140 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
276 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| D | ima_main.c | 810 int violation = 0; in process_buffer_measurement() local
864 ret = ima_store_template(entry, violation, NULL, buf, pcr); in process_buffer_measurement()
|
| /Linux-v5.10/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.10/drivers/infiniband/hw/hfi1/ |
| D | pcie.c | 779 u32 violation; in load_eq_table() local
795 PCIE_CFG_REG_PL105, &violation); in load_eq_table()
802 if (violation in load_eq_table()
|
| /Linux-v5.10/arch/m68k/ifpsp060/ |
| D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | sysfs-bus-usb | 105 Note that some devices, in violation of the USB spec, have a
|
| /Linux-v5.10/drivers/media/platform/qcom/camss/ |
| D | camss-vfe-4-1.c | 919 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
921 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| D | camss-vfe-4-7.c | 1041 u32 violation = readl_relaxed(vfe->base + VFE_0_VIOLATION_STATUS); in vfe_violation_read() local
1043 pr_err_ratelimited("VFE: violation = 0x%08x\n", violation); in vfe_violation_read()
|
| /Linux-v5.10/drivers/memory/ |
| D | Kconfig | 159 represents a coherency violation.
|
| /Linux-v5.10/drivers/base/firmware_loader/ |
| D | Kconfig | 59 then it may be a violation of the GPL to distribute the resulting
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | URB.rst | 191 cause a memory-access violation. The driver is responsible for avoiding this,
|
| /Linux-v5.10/Documentation/block/ |
| D | data-integrity.rst | 102 concept of an end-to-end protection scheme is a layering violation.
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | libata.rst | 665 HSM violation
816 `HSM violation <#excatHSMviolation>`__.
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | mmu.rst | 296 - guest page fault (or npt page fault, or ept violation)
|
| /Linux-v5.10/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 442 protected by the receiving host or if acceptance may result in violation of
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 621 think your computer was broken. It would be a violation of the
1058 violation of the read-write coherence rule. Similarly, if we had
1064 overwrite W', in violation of the write-write coherence rule.
1665 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
|
| /Linux-v5.10/Documentation/locking/ |
| D | lockdep-design.rst | 170 any rule violation between the new lock and any of the held locks.
|
| /Linux-v5.10/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 879 mask PROTO_VIOLATION 0x20|SEQINT /* SCSI protocol violation */
|
