| /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()
129 * ima_add_violation - add violation to measurement list.
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()
372 int violation = 0; in ima_store_measurement()
390 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
367 int violation = 0; ima_store_measurement() local
|
| H A D | ima_queue.c | 242 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_reboot_notifier()
266 if (!violation && !IS_ENABLED(CONFIG_IMA_DISABLE_HTABLE)) { in ima_init_digests()
282 if (violation) /* invalidate pcr */ in ima_init_digests()
166 ima_add_template_entry(struct ima_template_entry * entry,int violation,const char * op,struct inode * inode,const unsigned char * filename) ima_add_template_entry() argument
|
| H A D | ima_template_lib.c | 325 * If digest is NULL, the event being recorded is a violation. in ima_eventdigest_init_common()
357 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_init()
415 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ng_init()
439 if (event_data->violation) /* recording a violation. */ in ima_eventdigest_ngv2_init()
468 if (event_data->violation) { in ima_eventdigest_modsig_init()
469 /* Recording a violation. */ in ima_eventdigest_modsig_init()
|
| H A D | ima.h | 90 const char *violation;
212 * integrity violation (a file that is already opened for read is opened for in ima_inode_get_iint()
215 * IMA_EMITTED_OPENWRITERS - indicates to add open-writers integrity violation
302 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_hash_key()
450 int ima_store_template(struct ima_template_entry *entry, int violation,
77 const char *violation; global() member
|
| H A D | ima_main.c | 1118 int violation = 0; in process_buffer_measurement() local
1190 ret = ima_store_template(entry, violation, NULL, event_data.buf, pcr); in process_buffer_measurement()
|
| /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
|
| H A D | threat-model.rst | 95 However, bugs that permit one violation only once another one was already
|
| /linux/drivers/thermal/qcom/ |
| H A D | Kconfig | 35 interrupts are forwarded to the thermal framework as trip-violation
|
| /linux/arch/m68k/ifpsp060/ |
| H A D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /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/Documentation/ABI/stable/ |
| H A D | sysfs-bus-usb | 105 Note that some devices, in violation of the USB spec, have a
|
| /linux/Documentation/userspace-api/ |
| H A D | rseq.rst | 232 if it detects a violation.
|
| /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/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/arch/loongarch/ |
| H A D | Kconfig | 597 machanism for PCIe devices (this is a PCIe protocol violation, which
|
| /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
|
| /linux/Documentation/core-api/ |
| H A D | dma-api.rst | 729 do not violate those constraints. In the worst case such a violation can
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_pstate.rst | 275 it to a lower one unless in a thermal stress or a power limit violation
|