| /Linux-v5.4/security/integrity/ima/ |
| D | ima_api.c | 92 int violation, struct inode *inode, in ima_store_template() argument
104 if (!violation) { in ima_store_template()
121 result = ima_add_template_entry(entry, violation, op, inode, filename); in ima_store_template()
141 .violation = cause }; in ima_add_violation()
142 int violation = 1; in ima_add_violation() local
153 result = ima_store_template(entry, violation, inode, in ima_add_violation()
310 int violation = 0; in ima_store_measurement() local
328 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
|
| D | ima_queue.c | 164 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_add_template_entry() argument
175 if (!violation) { in ima_add_template_entry()
191 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| D | ima_init.c | 51 int violation = 0; in ima_add_boot_aggregate() local
77 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| D | ima.h | 64 const char *violation; member
134 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
225 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| D | ima_template_lib.c | 282 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
320 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
346 if (event_data->violation) { in ima_eventdigest_modsig_init()
|
| D | ima_main.c | 650 int violation = 0; in process_buffer_measurement() local
671 ret = ima_store_template(entry, violation, NULL, buf, pcr); in process_buffer_measurement()
|
| /Linux-v5.4/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 | 103 effective deterrent in our community. In case a violation happens the
105 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.4/Documentation/devicetree/bindings/rtc/ |
| D | imxdi-rtc.txt | 11 - interrupts: dryice security violation interrupt (second entry)
|
| /Linux-v5.4/Documentation/x86/ |
| D | intel_mpx.rst | 64 information about the violation in the 'struct siginfo'.
103 * bounds violation caused by MPX instructions.
173 If a #BR is generated due to a bounds violation caused by MPX.
174 We need to decode MPX instructions to get violation address and
192 The '_addr' field refers to violation address, and new '_addr_and'
196 can get violation address and bounds when bounds violations occur.
|
| /Linux-v5.4/drivers/infiniband/hw/hfi1/ |
| D | pcie.c | 771 u32 violation; in load_eq_table() local
787 PCIE_CFG_REG_PL105, &violation); in load_eq_table()
794 if (violation in load_eq_table()
|
| /Linux-v5.4/arch/m68k/ifpsp060/ |
| D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-bus-usb | 103 Note that some devices, in violation of the USB spec, have a
|
| /Linux-v5.4/drivers/memory/ |
| D | Kconfig | 124 represents a coherency violation.
|
| /Linux-v5.4/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.4/drivers/base/firmware_loader/ |
| D | Kconfig | 59 then it may be a violation of the GPL to distribute the resulting
|
| /Linux-v5.4/Documentation/block/ |
| D | data-integrity.rst | 102 concept of an end-to-end protection scheme is a layering violation.
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | URB.rst | 191 cause a memory-access violation. The driver is responsible for avoiding this,
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 167 any rule violation between the new lock and any of the held locks.
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | libata.rst | 665 HSM violation
816 `HSM violation <#excatHSMviolation>`__.
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 621 think your computer was broken. It would be a violation of the
1054 violation of the read-write coherence rule. Similarly, if we had
1060 overwrite W', in violation of the write-write coherence rule.
1644 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | mmu.txt | 277 - guest page fault (or npt page fault, or ept violation)
|
