| /Linux-v4.19/security/integrity/ima/ |
| D | ima_api.c | 90 int violation, struct inode *inode, in ima_store_template() argument
102 if (!violation) { in ima_store_template()
119 result = ima_add_template_entry(entry, violation, op, inode, filename); in ima_store_template()
138 int violation = 1; in ima_add_violation() local
149 result = ima_store_template(entry, violation, inode, in ima_add_violation()
289 int violation = 0; in ima_store_measurement() local
301 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
|
| D | ima_queue.c | 162 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_add_template_entry() argument
173 if (!violation) { in ima_add_template_entry()
189 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| D | ima_init.c | 55 int violation = 0; in ima_add_boot_aggregate() local
81 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| D | ima.h | 67 const char *violation; member
133 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
208 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| D | ima_template_lib.c | 278 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
316 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
|
| /Linux-v4.19/Documentation/process/ |
| D | kernel-enforcement-statement.rst | 24 However, if you cease all violation of this License, then your license
28 fails to notify you of the violation by some reasonable means prior to
33 violation by some reasonable means, this is the first time you have
34 received notice of violation of this License (for any work) from that
35 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 | 1.Intro.rst | 194 a result, their distribution is a violation of the GNU General Public
|
| /Linux-v4.19/Documentation/devicetree/bindings/rtc/ |
| D | imxdi-rtc.txt | 11 - interrupts: dryice security violation interrupt (second entry)
|
| /Linux-v4.19/Documentation/x86/ |
| D | intel_mpx.txt | 58 information about the violation in the 'struct siginfo'.
96 * bounds violation caused by MPX instructions.
166 If a #BR is generated due to a bounds violation caused by MPX.
167 We need to decode MPX instructions to get violation address and
185 The '_addr' field refers to violation address, and new '_addr_and'
189 can get violation address and bounds when bounds violations occur.
|
| /Linux-v4.19/drivers/infiniband/hw/hfi1/ |
| D | pcie.c | 801 u32 violation; in load_eq_table() local
817 PCIE_CFG_REG_PL105, &violation); in load_eq_table()
824 if (violation in load_eq_table()
|
| /Linux-v4.19/arch/m68k/ifpsp060/ |
| D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-bus-usb | 103 Note that some devices, in violation of the USB spec, have a
|
| /Linux-v4.19/drivers/memory/ |
| D | Kconfig | 115 represents a coherency violation.
|
| /Linux-v4.19/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-v4.19/drivers/base/firmware_loader/ |
| D | Kconfig | 55 then it may be a violation of the GPL to distribute the resulting
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | URB.rst | 191 cause a memory-access violation. The driver is responsible for avoiding this,
|
| /Linux-v4.19/Documentation/block/ |
| D | data-integrity.txt | 98 concept of an end-to-end protection scheme is a layering violation.
|
| /Linux-v4.19/Documentation/locking/ |
| D | lockdep-design.txt | 108 any rule violation between the new lock and any of the held locks.
|
| /Linux-v4.19/tools/memory-model/Documentation/ |
| D | explanation.txt | 625 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.
1629 taste of what is involved. Suppose we have a violation of the first
1666 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | libata.rst | 665 HSM violation
816 `HSM violation <#excatHSMviolation>`__.
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| D | mmu.txt | 278 - guest page fault (or npt page fault, or ept violation)
|
| /Linux-v4.19/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 442 protected by the receiving host or if acceptance may result in violation of
|
| /Linux-v4.19/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 879 mask PROTO_VIOLATION 0x20|SEQINT /* SCSI protocol violation */
|
