| /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_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()
1136 ret = ima_store_template(entry, violation, NULL, event_data.buf, pcr); in process_buffer_measurement()
1060 int violation = 0; process_buffer_measurement() local
|
| /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 | 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/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/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/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.
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 102 concept of an end-to-end protection scheme is a layering violation.
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 80 then it may be a violation of the GPL to distribute the resulting
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-driver-habanalabs | 226 Description: Check and display page fault or access violation mmu errors for
|
| /linux/Documentation/driver-api/usb/ |
| H A D | URB.rst | 191 cause a memory-access violation. The driver is responsible for avoiding this,
|
| /linux/Documentation/driver-api/ |
| H A D | libata.rst | 635 HSM violation
786 `HSM violation <#excatHSMviolation>`__.
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | mmu.rst | 322 - guest page fault (or npt page fault, or ept violation)
|
| /linux/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 442 protected by the receiving host or if acceptance may result in violation of
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 170 any rule violation between the new lock and any of the held locks.
|
| /linux/drivers/scsi/aic7xxx/ |
| H A D | aic7xxx.reg | 879 mask PROTO_VIOLATION 0x20|SEQINT /* SCSI protocol violation */
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 133 resulting from policy violation.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 674 think your computer was broken. It would be a violation of the
1141 violation of the read-write coherence rule. Similarly, if we had
1147 overwrite W', in violation of the write-write coherence rule.
1748 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
|