Home
last modified time | relevance | path

Searched full:violation (Results 1 – 25 of 306) sorted by relevance

12345678910>>...13

/linux-6.14.4/drivers/soc/mediatek/
Dmtk-devapc.c47 /* numbers of violation index */
103 * devapc_sync_vio_dbg - do "shift" mechansim" to get full violation information.
106 * When violation is triggered, violation info is kept
108 * Driver should do shift mechansim to sync full violation
128 /* Find the minimum shift group which has violation */ in devapc_sync_vio_dbg()
144 dev_err(ctx->dev, "%s: Shift violation info failed\n", __func__); in devapc_sync_vio_dbg()
158 * devapc_extract_vio_dbg - extract full violation information after doing
173 /* Print violation information */ in devapc_extract_vio_dbg()
175 dev_info(ctx->dev, "Write Violation\n"); in devapc_extract_vio_dbg()
177 dev_info(ctx->dev, "Read Violation\n"); in devapc_extract_vio_dbg()
[all …]
DKconfig24 This driver is mainly used to handle the violation which catches
26 The violation information is logged for further analysis or
/linux-6.14.4/Documentation/process/
Dcode-of-conduct-interpretation.rst52 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
174 behavior and make amends for it in the setting the violation has taken place.
198 Seek public apology for the violation
202 setting in which the violation has taken place, seeking public apology
203 for the violation.
205 A public apology for the violation is the first step towards rebuilding
209 Remedial measures if there is no public apology for the violation
Dkernel-enforcement-statement.rst26 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
Dembargoed-hardware-issues.rst104 the received information confidential. Violation of the pledge will lead to
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-6.14.4/security/integrity/ima/
Dima_api.c103 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()
127 * ima_add_violation - add violation to measurement list.
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()
365 int violation = 0; in ima_store_measurement() local
383 result = ima_store_template(entry, violation, inode, filename, pcr); in ima_store_measurement()
Dima_template_lib.c325 * 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()
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()
468 /* Recording a violation. */ in ima_eventdigest_modsig_init()
Dima_queue.c166 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()
Dima_init.c54 int violation = 0; in ima_add_boot_aggregate() local
88 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
/linux-6.14.4/arch/arc/kernel/
Dentry-compact.S32 * exception. Thus FAKE RTIE needed in low level Priv-Violation handler.
107 VECTOR EV_TLBProtV ; 0x118, Protection Violation (0x23)
109 VECTOR EV_PrivilegeV ; 0x120, Privilege Violation (0x24)
252 ; Protection Violation Exception Handler
259 ;------ (5) Type of Protection Violation? ----------
262 ; -Access Violation : 00_23_(00|01|02|03)_00
267 ;========= (6a) Access Violation Processing ========
Dentry-arcv2.S36 VECTOR EV_TLBProtV ; Protection Violation
37 VECTOR EV_PrivilegeV ; Privilege Violation
149 ; Protection Violation Exception Handler
/linux-6.14.4/drivers/rtc/
Drtc-imxdi.c72 #define DSR_SVF (1 << 0) /* Security Violation Flag */
79 #define DIER_SVIE (1 << 0) /* Security-violation Interrupt Enable */
295 "The security violation has happened at %u seconds\n", in di_handle_invalid_state()
388 * now we are trying to clear the "Security-violation flag" to in di_handle_invalid_and_failure_state()
397 "Cannot clear the security violation flag. We are ending up in an endless loop!\n"); in di_handle_invalid_and_failure_state()
658 * interrupt handler for dryice "normal" and security violation interrupt
669 /* handle the security violation event */ in dryice_irq()
681 /* report the violation */ in dryice_irq()
764 /* the 2nd irq is the security violation irq in dryice_rtc_probe()
809 dev_warn(&pdev->dev, "security violation interrupt not available.\n"); in dryice_rtc_probe()
/linux-6.14.4/arch/nios2/mm/
Dfault.c34 #define EXC_X_PROTECTION_FAULT 13 /* TLB permission violation (x) */
35 #define EXC_R_PROTECTION_FAULT 14 /* TLB permission violation (r) */
36 #define EXC_W_PROTECTION_FAULT 15 /* TLB permission violation (w) */
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-pci-devices-aer_stats56 ACS Violation 0
86 ACS Violation 0
/linux-6.14.4/drivers/gpu/drm/v3d/
Dv3d_irq.c147 dev_err(v3d->drm.dev, "GMP violation\n"); in v3d_irq()
212 ", write violation" : ""), in v3d_hub_irq()
221 dev_err(v3d->drm.dev, "GMP Violation\n"); in v3d_hub_irq()
/linux-6.14.4/drivers/memory/tegra/
Dmc.c735 [ 8] = "Security violation",
739 [12] = "VPR violation",
740 [13] = "Secure carveout violation",
741 [16] = "MTS carveout violation",
742 [17] = "Generalized carveout violation",
748 [3] = "TrustZone violation",
749 [4] = "Carveout violation",
/linux-6.14.4/lib/
DKconfig.ubsan32 when a UBSAN violation occurs. (Except on arm64 and x86, which
35 out the details of a UBSAN violation. It makes the kernel log
/linux-6.14.4/include/soc/at91/
Dat91sam9_ddrsdr.h120 #define AT91_DDRSDRC_WPVS (1 << 0) /* Write protect violation status */
121 #define AT91_DDRSDRC_WPVSRC (0xffff << 8) /* Write protect violation source */
/linux-6.14.4/Documentation/devicetree/bindings/rtc/
Dimxdi-rtc.yaml22 - description: dryice security violation interrupt
/linux-6.14.4/arch/nios2/kernel/
Dentry.S87 .word protection_exception_pte /* 13 - TLB permission violation (x) */
88 .word protection_exception_pte /* 14 - TLB permission violation (r) */
89 .word protection_exception_pte /* 15 - TLB permission violation (w) */
91 .word unhandled_exception /* 16 - MPU region violation */
/linux-6.14.4/arch/x86/include/asm/
Dtrap_pf.h18 * bit 31 == 1: fault was due to RMP violation
/linux-6.14.4/drivers/iommu/
Dfsl_pamu.c448 * & enable PAMU access violation interrupts. in setup_one_pamu()
503 pr_emerg("access violation interrupt\n"); in pamu_av_isr()
538 /* clear access violation condition */ in pamu_av_isr()
542 /* check if we got a violation for a disabled LIODN */ in pamu_av_isr()
546 * violation can be reported for a disabled in pamu_av_isr()
548 * access violation reporting. in pamu_av_isr()
/linux-6.14.4/drivers/memory/
Dfsl-corenet-cf.c74 #define ERRDET_CV (1 << 1) /* Coherency Violation */
152 dev_crit(ccf->dev, "Coherency Violation\n"); in ccf_irq()
/linux-6.14.4/Documentation/devicetree/bindings/soc/mediatek/
Ddevapc.yaml13 The security violation is logged and sent to the processor for further
/linux-6.14.4/include/linux/fsl/bestcomm/
Dfec.h30 #define BCOM_FEC_RX_BD_LG 0x00200000ul /* Rx frame length violation */

12345678910>>...13